Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Le jeudi 07 août 2008 à 18:52 +0000, Karen Tracey a écrit : > Karen Tracey <[EMAIL PROTECTED]> added the comment: > > Cool, thanks! Do I take it from the Versions setting that the fix will > be available in the next 2.6 beta but not get propagated to prior > releases? (I'm not very familiar with this issue tracker so am just > trying to understand what the various fields mean.)
Indeed, the fix will be present in the next 2.6 beta. As for the 2.5 branch, it is in maintenance mode and we want to minimize the amount the potential breakage that we might cause there. I don't think the present bug is important enough to warrant a backport, but other developers may disagree and fix 2.5 as well :-) (as for 3.0, it is unaffected) _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1288615> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
