On Fri, 12 Aug 2016, Chris Jones wrote: > On 11/08/16 20:40, Fred Wright wrote: [...] > > Well, leaving something alone that's working just fine is hardly much of a > > maintenance burden. > > On the other hand, whats the rationale for keeping 2.6, given 2.7 is the > official upstream production version of the 2.x series. What use case > requires 2.6 and cannot move to 2.7 ?
Testing code against 2.6 (among others), because it's intended to run on a wide range of platforms, and one wants to make as few assumptions as possible about what Python version(s) the end user might have installed. Some distros lag *way* behind in versions of various things, including Python. If the python.org folks had their way, all 2.x versions would be eradicated, but there were too many pitchforks at the gates to let that happen. :-) Fred Wright _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
