Eric Smith eric at trueblade.com
Mon Mar 21 16:24:24 CET 2011

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

Only that it takes one extra release to go from
pending->deprecated->removed, as opposed to deprecated->removed.

Eric.

---

• 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 ]

---

More information about the Python-Dev mailing list