R. David Murray added the comment:

Neil: I presume you are speaking of your in-progress PEP patch, and not the 
current python code?  If so, please keep the discussion of handling this in the 
context of the PEP to the PEP issue.  This issue should be for resolving the 
bug in the current code (if we choose to do so...if the PEP gets accepted for 
3.5 this issue may become irrelevant, as I'm not sure we'd want to fix it in 
3.4 for backward compatibility reasons).


Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list

Reply via email to