Python versions for new python ports?

[Frank Schima]

On Nov 13, 2013, at 7:04 AM, Rainer Müller <raimue at macports.org> wrote:

> On 2013-11-12 21:51, Frank Schima wrote:
>>>> On Tue, 12 Nov 2013 15:26:20 -0500, Peter Danecek <Peter.Danecek at bo.ingv.it> wrote:
>>>> 
>>>>> Anyway, I wonder if there is a clearly defined policy on which Python versions should be included for new ports.
>>> 
>>> So is there any clear line on this?
>> 
>> I don't think we have a stated policy. Personally, I would not even add a python 26, 31 or 32 versions unless you need it or someone requests one. Why support anything but the current versions of python for a new port?
> 
> Then what is the intention of adding multiple pythonXY ports after all and not just python2 with py2-* and python3 with py3-*?
> We invested a lot of work to switch from multiple pythonXY port groups to a single unified ports group that provides different subports for each version.
> 
> There was a demand for multiple versions of python when python25 was added to MacPorts in addition to python24. I dug out these old threads reasoning on what to do and which eventually lead to the duplication of ports for python modules:
> 
> https://lists.macosforge.org/pipermail/macports-dev/2007-February/000652.html
> https://lists.macosforge.org/pipermail/macports-dev/2007-February/000657.html
> https://lists.macosforge.org/pipermail/macports-users/2007-September/005364.html

I was only saying that for a new python module we should support the currently supported python versions. I totally agree with all the good work in Macports to support multiple pythons. The split between python 2 and 3 is reason enough. And we need to do this to support new versions of python going forward. This allows people to move to the newer python versions at their own pace. I'm just suggesting that we do not move backwards for a new module.  When a hypothetical python 2.8 or 3.5 comes out, this port can easily be modified to add versions for them. Plus, as mentioned by jmr in another post, if someone requests an older version, we can easily add that too if upstream supports it. But why include older python versions up front if no one needs it?


Cheers!
Frank