Guido van Rossum added the comment: I am okay with making it a silent warning.
Can we do it in two stages though? It doesn't have to be two releases, I just mean two separate commits: (1) fix all places in the stdlib that violate this principle; (2) separately commit the code that causes the silent deprecation (and tests for it). What exactly was the hard crash you got? Do you think it was a bug in your own C code or in existing C code? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27364> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
