R. David Murray added the comment:

I played around with this for a bit, but I couldn't come up with any test 
improvements, or any way to test the bug that is being fixed.  So I just 
committed it as is.  Thanks, Serhiy.  And thanks Vajrasky for giving it a try 
and figuring out some of the stuff that *doesn't* work as a fix :)

I decided to only commit this to 3.4.  I don't think the risk of an unexpected 
behavior change in a maintenance release is worth the relatively small benefit 
that this fix provides.

----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed
versions:  -Python 3.3

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue18116>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to