RetroSearch Browse

Mon Mar 21 16:39:59 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-March/109677.html

On Mon, 21 Mar 2011 11:24:24 -0400 (EDT)
"Eric Smith" <eric at trueblade.com> wrote:
> >>
> >> >> Given the recent discussion about backwards compatibility: what's
> >> >> the best approach? What warning should be emitted, if any?
> >> >> (the warning would only be generated if an s# or similar format
> >> >>  was actually encountered - not just if merely PyArg_ParseTuple is
> >> >>  called).
> >> >
> >> > I'd say a DeprecationWarning. They are quiet by default anyway...
> >>
> >> Why not a PendingDeprecationWarning?
> >
> > Is there still a difference?
> 
> Only that it takes one extra release to go from
> pending->deprecated->removed, as opposed to deprecated->removed.

Well, some things have been issueing deprecation warnings for several
releases, I think. And given Guido's latest stance on the subject we
may see more of them in the future.

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109677.html below:

[Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple