Gregory P. Smith <g...@krypto.org> added the comment: trunk r70878 has the code issue an actual PendingDeprecationWarning for the fail* methods and documents them as deprecated. If anyone has a better idea of a better way to state those deprecations in the docs, feel free to jump in here.
I was unaware of the PendingDeprecationWarning (ignored by default) prior to this. I think that is what Guido was suggesting. The question of if we can do an actual DeprecationWarning for 3.1 or not still stands. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue2578> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
