<div dir="ltr">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.<div>
<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 22, 2014 at 12:25 PM, Frank Schima <span dir="ltr"><<a href="mailto:macsforever2000@macports.org" target="_blank">macsforever2000@macports.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
<br>
Cheers!<br>
<span class="HOEnZb"><font color="#888888">Frank<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Jan 22, 2014, at 9:11 AM, Jeremy Lavergne <<a href="mailto:jeremy@lavergne.gotdns.org">jeremy@lavergne.gotdns.org</a>> wrote:<br>
<br>
> Those packages were blocking the removal of python24 subports that I maintain (e.g py-elementtree).<br>
><br>
> 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.<br>
><br>
> 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.<br>
><br>
> Realistically, most modules below python27 should get axed.<br>
><br>
> On Jan 22, 2014, at 10:53, Sean Farley <<a href="mailto:sean@macports.org">sean@macports.org</a>> wrote:<br>
><br>
>><br>
>> <a href="mailto:jmr@macports.org">jmr@macports.org</a> writes:<br>
>><br>
>>> Instead of deleting a few random py24 subports, why don't you ask the<br>
>>> python24 maintainer and the -users list if anyone still needs python<br>
>>> 2.4? (They said yes last time we asked.) And if they don't, make a<br>
>>> ticket for deleting python24 and either deleting or updating to a newer<br>
>>> python for all its dependents.<br>
>><br>
>> I would like to not get rid of python24 anytime soon because it allows<br>
>> me to test compatibility. I am not opposed, however, to removing all the<br>
>> py24-* ports (maybe all but virtualenv and friends?).<br>
>> _______________________________________________<br>
>> macports-dev mailing list<br>
>> <a href="mailto:macports-dev@lists.macosforge.org">macports-dev@lists.macosforge.org</a><br>
>> <a href="https://lists.macosforge.org/mailman/listinfo/macports-dev" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-dev</a><br>
><br>
> _______________________________________________<br>
> macports-dev mailing list<br>
> <a href="mailto:macports-dev@lists.macosforge.org">macports-dev@lists.macosforge.org</a><br>
> <a href="https://lists.macosforge.org/mailman/listinfo/macports-dev" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-dev</a><br>
<br>
_______________________________________________<br>
macports-dev mailing list<br>
<a href="mailto:macports-dev@lists.macosforge.org">macports-dev@lists.macosforge.org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-dev" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-dev</a><br>
</div></div></blockquote></div><br></div>