Guido van Rossum added the comment:

BTW, I screwed up and committed this into the public 3.5 repo first (and merged 
from there into default). I guess once Larry has merged the fix into his 
special closed 3.5 bitbucket repo I should do a null merge from there back to 
public 3.5 and forward the null merge to 3.6 as well.

----------

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

Reply via email to