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

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

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

• Previous message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
• Next message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 
> >> 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?

• Previous message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
• Next message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4