Re: [116220] trunk/dports/python
j...@macports.org writes: Revision: 116220 https://trac.macports.org/changeset/116220 Author: snc at macports.org Date: 2014-01-21 13:14:00 -0800 (Tue, 21 Jan 2014) Log Message: --- py-turbogears, py-turbokid: remove python24, maintainer timeout #35623 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@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [116220] trunk/dports/python
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 s...@macports.org wrote: j...@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@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [116220] trunk/dports/python
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 jer...@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 s...@macports.org wrote: j...@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@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [116220] trunk/dports/python
The one thing I'd caution against is removing any py24* ports that have no newer versions. I cannot think of any off the top of my head, but I guess that would just be something to check for while removing the py24* ports, i.e., making sure that they have a version available for a newer python before removing it. On Wed, Jan 22, 2014 at 12:25 PM, Frank Schima macsforever2...@macports.org wrote: 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 jer...@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 s...@macports.org wrote: j...@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@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
[116220] trunk/dports/python
Revision: 116220 https://trac.macports.org/changeset/116220 Author: snc at macports.org Date: 2014-01-21 13:14:00 -0800 (Tue, 21 Jan 2014) Log Message: --- py-turbogears, py-turbokid: remove python24, maintainer timeout #35623 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. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
