On 2013-11-12 21:51, Frank Schima wrote: >>> On Tue, 12 Nov 2013 15:26:20 -0500, Peter Danecek >>> <peter.dane...@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 Rainer _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
