[issue2705] incompatible change to warnings.showwarning

[Brett Cannon]

Brett Cannon <brett at python.org> added the comment:

On Thu, May 1, 2008 at 7:29 PM, Benjamin Peterson
<report at bugs.python.org> wrote:
>
>  Benjamin Peterson <musiccomposition at gmail.com> added the comment:
>
>  Why don't you add a Py3k warning and keep it in Py3k?

Just asked python-dev if they are okay with that. 2.6 could get a
PendingDeprecationWarning and 3.0 could get a DeprecationWarning. But
I don't want to do an API change between the two that breaks code like
that.

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2705>
__________________________________