[issue14614] PyTuple_SET_ITEM could check bounds in debug mode

STINNER Victor added the comment: Since bpo-35337 has been rejected, I also close this issue. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___

[issue14614] PyTuple_SET_ITEM could check bounds in debug mode

STINNER Victor added the comment: Oh, I didn't know this old issue (6 years old). I wrote an implementation of this issue for PyTuple_GET_ITEM/SET_ITEM: bpo-35337. Would you mind to have a look? It seems to be backward incompatible when these macros are misused on structseq. -- nosy

[issue14614] PyTuple_SET_ITEM could check bounds in debug mode

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue14614] PyTuple_SET_ITEM could check bounds in debug mode

Brett Cannon added the comment: Should we limit ourselves to bound errors? Couldn't we make the macros aliases for their full-fledged function equivalents (e.g. PyTuple_SetItem()) which trigger Py_FatalError() on error so we also get argument type checking? -- nosy: +brett.cannon ___

[issue14614] PyTuple_SET_ITEM could check bounds in debug mode

Benjamin Peterson added the comment: Also, PyList_SET_ITEM and friends. -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue14614] PyTuple_SET_ITEM could check bounds in debug mode

New submission from Antoine Pitrou : Which it doesn't, as exemplified in e8c87226bcb3 :-) -- components: Interpreter Core messages: 158632 nosy: benjamin.peterson, ncoghlan, pitrou priority: low severity: normal status: open title: PyTuple_SET_ITEM could check bounds in debug mode type: