gh-50333: Deprecate support of non-tuple sequences in PyArg_ParseTuple() - #128374
Conversation
Sorry, something went wrong.
…seTuple() Non-tuple sequences are deprecated as argument for the "(items)" format unit in PyArg_ParseTuple() and other argument parsing functions if items contains format units which store borrowed buffer or reference (e.g. "s" and "O"). str and bytearray are no longer accepted as valid sequences.
There was a problem hiding this comment.
While I understand that "borrowed buffer or reference" reads as "borrowed buffer or borrowed reference", I would advise repeating "borrowed reference" as well.
I haven't looked at te implementation though.
Sorry, something went wrong.
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com> Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
In this case, I think we should consider being explicit, rather than worrying about the repeated word. |
Sorry, something went wrong.
Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
|
This didn't cause much controversy when posted on Discourse, so I just merge it. There will be time to tweak or revert it. |
Sorry, something went wrong.
Non-tuple sequences are deprecated as argument for the "(items)" format unit in PyArg_ParseTuple() and other argument parsing functions if items contains format units which store borrowed buffer or reference (e.g. "s" and "O").
str and bytearray are no longer accepted as valid sequences.
📚 Documentation preview 📚: https://cpython-previews--128374.org.readthedocs.build/