STINNER Victor added the comment: Barry wrote on python-dev mailing list: "If it's documented to behave that way, why would you still consider it a bug? The current behavior is clearly intentional, the function is working as intended, and there may be code out there that depends on this documented functionality, or at least, it won't be prepared to handle the new exception." http://mail.python.org/pipermail/python-dev/2012-October/122122.html
So I'm closing the issue. ---------- resolution: -> wont fix status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16153> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
