R. David Murray added the comment: We use the versions field to indicate which versions it might get fixed in. Since this is not a security issue, that would be 3.5 and 3.6, if it doesn't affect 2.7. If we decide to make the code match the docs, it will probably only get fixed in 3.6, since it is a behavior change.
---------- nosy: +r.david.murray versions: -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27583> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
