Mark Dickinson <dicki...@gmail.com> added the comment: I'm not going to backport this to 2.6. The problem is that the fix for this issue is tied up with the corresponding change to str (str(1e11) produces '1e+11' in trunk and 100000000000.0 in release26-maint); I daren't change str() in 2.6, so backporting would mean separating out the str and format changes.
I'm not opposed to the backport itself; it's just a lack of time and confidence of getting it right on my part. If anyone else wants to backport feel free. ---------- assignee: marketdickinson -> _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5864> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
