Re: End of Python 2.4–2.6 and 3.1–3.3 support

Ryan Schmidt ryandesign at
Sat Oct 11 04:27:33 PDT 2014

On Oct 11, 2014, at 4:23 AM, René J.V. Bertin wrote:

> On Friday October 10 2014 23:56:09 Lawrence Velázquez wrote:
>> Ports using these series will be migrated to Python 2.7 or 3.4 as appropriate. New ports will only use 2.7 and 3.4 (and 3.5, when it is released).
> Will there also be support for cleaning up the ports being replaced, rather than leaving that up to us once we start getting errors (as was the case with the migration from perl 5.12)?

What exactly do you mean by "cleaning up"? I've already seen many commits go through with old python ports being added to the new "py-graveyard" port. This should facilitate upgrades by making the old ports "replaced_by" the new versions. The old ports will show up in "port outdated", and the user can upgrade them with "sudo port upgrade outdated". The method for the user to uninstall the old versions would be the same as it's always been, e.g. "sudo port uninstall inactive".

More information about the macports-users mailing list