Issue 14614: PyTuple_SET_ITEM could check bounds in debug mode
Created on 2012-04-18 15:03 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (5) | |||
|---|---|---|---|
| msg158632 - (view) | Author: Antoine Pitrou (pitrou) *  |
Date: 2012-04-18 15:03 | |
Which it doesn't, as exemplified in e8c87226bcb3 :-) |
|||
| msg158633 - (view) | Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2012-04-18 15:23 | |
Also, PyList_SET_ITEM and friends. |
|||
| msg158731 - (view) | Author: Brett Cannon (brett.cannon) * |
Date: 2012-04-19 14:19 | |
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? |
|||
| msg330642 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2018-11-29 00:23 | |
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. |
|||
| msg333454 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2019-01-11 10:52 | |
Since bpo-35337 has been rejected, I also close this issue. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:29 | admin | set | github: 58819 |
| 2019-01-11 10:52:42 | vstinner | set | status: open -> closed resolution: wont fix messages: + msg333454 stage: resolved |
| 2018-11-29 00:23:46 | vstinner | set | nosy:
+ vstinner messages: + msg330642 |
| 2012-04-20 06:40:35 | Arfrever | set | nosy:
+ Arfrever |
| 2012-04-19 14:19:07 | brett.cannon | set | nosy:
+ brett.cannon messages: + msg158731 |
| 2012-04-18 15:23:10 | benjamin.peterson | set | messages: + msg158633 |
| 2012-04-18 15:03:33 | pitrou | create | |