[116220] trunk/dports/python

[Frank Schima]

I agree. I think all py24-* ports should be removed now. Removing py24-* ports will change the default python to 2.7 for people who (mistakenly) install py-foo. I would not object to everything less than py27-* leaving too but maybe later. 


Cheers!
Frank

On Jan 22, 2014, at 9:11 AM, Jeremy Lavergne <jeremy at lavergne.gotdns.org> wrote:

> Those packages were blocking the removal of python24 subports that I maintain (e.g py-elementtree).
> 
> 100% agree with removing at least the python24 modules like Sean said. Also, people are quite capable of pulling python24’s modules out of our repository after removal if they need them.
> 
> While Sean has a use for python24 itself, it has security problems and is not supported. I feel it also should get removed and used in a local repository if possible, but I’m perfectly content with doing just modules for now.
> 
> Realistically, most modules below python27 should get axed.
> 
> On Jan 22, 2014, at 10:53, Sean Farley <sean at macports.org> wrote:
> 
>> 
>> jmr at macports.org writes:
>> 
>>> Instead of deleting a few random py24 subports, why don't you ask the
>>> python24 maintainer and the -users list if anyone still needs python
>>> 2.4? (They said yes last time we asked.) And if they don't, make a
>>> ticket for deleting python24 and either deleting or updating to a newer
>>> python for all its dependents.
>> 
>> I would like to not get rid of python24 anytime soon because it allows
>> me to test compatibility. I am not opposed, however, to removing all the
>> py24-* ports (maybe all but virtualenv and friends?).
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev