On Tue, Sep 16, 2014 at 8:19 AM, Christoph Deil <[email protected]> wrote: > > On 16 Sep 2014, at 07:44, Mojca Miklavec <[email protected]> wrote: > >> On Tue, Sep 16, 2014 at 7:30 AM, Clemens Lang wrote: >>> Hi, >>> >>> ----- On 16 Sep, 2014, at 03:56, Lawrence Velázquez [email protected] >>> wrote: >>> >>>> Is there some overwhelmingly good reason we still provide these, given >>>> that 2.7 >>>> is still alive and kicking? Can we please stop providing them? >>> >>> If I were you, I'd set a timeout and if nobody argues that we should keep >>> them >>> for a good reason, delete them once the timeout has passed. Probably ask >>> -users, >>> too. >>> >>> While we're at it, isn't 2.6 unsupported as well? >> >> Version 2.6 is still useful to allow installing things like >> py26-wxpython-2.8 and py27-wxpython-3.0 side-by-side without >> conflicts. But I totally support removing python 2.4 and 2.5. >> >> We could limit the use of 2.6 to ports like the one with wxWidgets and >> gradually remove 2.6 from the rest until we retire it completely. (I >> wouldn't oppose removing the ports that still depend on wxPython 2.8 a >> year or two from now.) > > I use the Macports Python 2.6 to test Python packages that support it (most > do). > So my vote would be to remove Python 2.4 and 2.5 (which almost no-one uses > and supports any more), but to keep Python 2.6.
Just to make it clear: I also vote to remove 2.4 + 2.5 and keep 2.6 for now. It just doesn't make much sense to me to spend precious time fixing problems with 2.6 to make it work on every latest and greatest OS X version. (Once again it would be nice to automatically uninstall all the py24-foo ports, but I don't know how to do that and I don't consider it to be a showstopper if we don't find an elegant solution soon.) Mojca _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
