Larry Hastings added the comment:

I think it's about time to think about releasing 3.5.1.  But since this bug is 
marked as a "release blocker", 3.5.1 cannot be released until this is fixed.  
Arguably I can't even really make a schedule for 3.5.1 until it's fixed, or at 
least I'm reasonably confident I know when it'll be fixed.

Any idea when this might be fixed?

----------
nosy: +larry

_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue25446>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to