Am 15.11.13 00:57, schrieb Chris Barker: > Maybe so -- but we are either maintaining 2.7 or not -- it WIL be > around for along time yet...
Procedurally, it's really easy. Ultimately it's up to the release manager to decide which changes go into a release and which don't, and Benjamin has already voiced an opinion. In addition, Guido van Rossum has voiced an opinion a while ago that he doesn't consider fixing bugs for 2.7 very useful, and would rather see maintenance focus on ongoing support for new operating systems, compiler, build environments, etc. The rationale is that people who have lived with the glitches of 2.x for so long surely have already made their work-arounds, so they aren't helped with receiving bug fixes. The same is true in your case: you indicated that you *already* work around the problem. It may have been tedious when you had to do it, but now it's done - and you might not even change your code even if Python 2.7.x gets changed, since you might want to support older 2.7.x release for some time. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
