I agree with all of this we only really need 27 and 33/34. --- TS http://www.southofheaven.org/ Life begins and ends with chaos, live between the chaos!
On Mar 20, 2014, at 9:20 AM, Daniel Johnson <daniel.johnso...@gmail.com> wrote: > > On Mar 20, 2014, at 9:40 AM, TheSin <the...@southofheaven.org> wrote: > >> I vote take out the axe, your python version options are getting out of hand >> honestly. >> --- >> TS >> http://www.southofheaven.org/ >> Life begins and ends with chaos, live between the chaos! >> >> On Mar 20, 2014, at 12:13 AM, Daniel Macks <dma...@netspace.org> wrote: >> >>> We've been dragging python26 along for years, since back when it was the >>> latest thing. It's not. Python27 has been available in fink for many years, >>> and even in the past several OS X versions. Upstream says "Python itself >>> has jumped to the 3.x series in 2008, with some major changes that may make >>> upgrading non-trivial in some cases, so it makes sense to keep "some" >>> python2.x in fink (OS X still has python27 and maybe older also). Upstream >>> plans to keep 27 in maintenance mode for at least a while longer but gave >>> up on even security patches for 26 as I understand it. >>> >>> As of yesterday, the only dependencies on python26 are the -py26 suite of >>> modules--there does not appear to be anything outside of this >>> self-contained tree. Is it time to chop down that tree? There are no -py26 >>> modules that do not have a parallel -py27 variant. Ordinarily, I'd not >>> object to keeping ancient versions of things around and just stop bringing >>> them forward when we roll the next Distribution, but python26 is also the >>> only package still using db48, another ancient version. I'd love to stop >>> having to support ancient versions of things that are not even getting >>> security-support upstream altogether. >>> >>> dan >>> >>> -- >>> Daniel Macks >>> dma...@netspace.org > > I agree. There's no reason to keep 2.6 around as 2.7 is fully backward > compatible. > > It's also reasonable to kill 3.1 as it's now unsupported upstream. 3.3 and > the just released 3.4 will stay of course, but we might also consider killing > 3.2 even though it still gets patches. 3.3 introduced better backward > compatibility with 2.7 to ease porting to 3.x and vastly improved unicode > string handling. > > There are no language changes between 3.3 and 3.4, just new and updated > library modules, so if maintainers can add 3.4 variants to their packages > that would be awesome. > > Daniel ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
