Python versions for new python ports?
Frank Schima
macsforever2000 at macports.org
Tue Nov 12 12:51:29 PST 2013
On Nov 12, 2013, at 1:48 PM, Peter Danecek <Peter.Danecek at bo.ingv.it> wrote:
> On Nov 12, 2013, at 21:41 , "Jeremy Lavergne" <jeremy at lavergne.gotdns.org> wrote:
>
>> To avoid creating pyXY-pyshp, you'd leave out XY in python.versions. You want to avoid 24 and 25 for your goal so python.versions should only have 26 27 31 32 33 34.
> Yes, I intentionally left the 2 older versions around as reminder. I will delete them, if there is consensus that 24 and 25 should not be included to new ports any more.
Definitely do not include 24 and 25.
>> 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?
Cheers!
Frank
More information about the macports-dev
mailing list