On Nov 12, 2013, at 21:51 , Frank Schima <macsforever2...@macports.org> wrote:
> 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? Well, in this case supporting seems not too problematic. Not sure, just some considerations. Python 2.6 's last bug fix release was only few days ago, and it is still found around in production, so for testing it may make sense. And, there are as still few modules available only for py26. Python 3.1 is probably not used a lot (so okay), but again 3.2 seems to have more modules available than 3.3. ~petr
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
