Thanks Pavel, this makes sense now. On Tue, May 15, 2018 at 5:30 AM, Pavel Petroshenko <pa...@petroshenko.com> wrote:
> Hi Dmitriy, > > PHP 5.6 and 7.0 are going to be end-of-life shortly [1]. So the minimal > version for the Thin Client is going to be either 7.1 or 7.2 (I would > finalize this along with the PHP Thin Client API proposal). > > As for Python, there is still some legacy code on 2.7, the oldest active > 2.x version. However the use of Python 2 is declining as it’s not actively > developed, doesn’t get new features, and its maintenance is going to be > stopped in 2020 [2]. Python 3 is a strong leader with 75% and Python 2 is > used as the main interpreter by only 25% (rapidly declining) [3]. So I'm > leaning towards supporting 3.4+ (the oldest active 3.x version). However, I > would keep the 2.7 in mind for API design. > > I hope it makes sense. > > Thanks, > p. > > [1] http://php.net/supported-versions.php > [2] https://legacy.python.org/dev/peps/pep-0373/ > [3] https://www.jetbrains.com/research/python-developers-survey-2017/ > > > On Sat, May 12, 2018 at 6:21 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > Pavel, > > > > Can you suggest what would be the advantages and disadvantages of > > supporting different versions? > > > > D. > > > > On Sat, May 12, 2018 at 7:21 AM, Pavel Petroshenko < > pa...@petroshenko.com> > > wrote: > > > > > Igniters, > > > > > > Are there any strong opinions on which language versions should the > Thin > > > Clients written in Python and PHP support? Any objections to using PHP > > 7.1+ > > > and Python 3.5+? > > > > > > Thanks, > > > > > > p. > > > > > >
