Ned Deily added the comment:

More specifically, the bug that causes the problem was first released in the 
2.7.6 release candidate 1 (pre-release, 2013-10-26) and fixed in the official 
2.7.6 final release (2013-11-10).  So it is somewhat surprising that you would 
continually re-encounter it.

----------
nosy: +ned.deily

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

Reply via email to