➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2004-05-10 20:01 by terry.reedy, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg20757 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2004-05-10 20:01 | |
Because the functions in the new module give direct access to API functions, syntactically legal code that uses them can be more fragile than normal -- leading to possible core dumps (which are normally considered to be interpreter bugs). Should Lib Ref 3.27 warn about this possibility? Can the interfacing be strengthened to cover at least some bad inputs? Can ceval be strengthed without slowing it down? |
|||
| msg20758 - (view) | Author: Raymond Hettinger (rhettinger) * |
Date: 2004-08-17 02:32 | |
Logged In: YES user_id=80475 Michael Hudson patched compile.c to make PyNew_Code less susceptible to bogus arguments. See Python/compile.c 2.315 Also, I expanded the warnings in the docs for the new module. See Doc/lib/libnew.tex 1.10. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:04 | admin | set | github: 40242 |
| 2004-05-10 20:01:52 | terry.reedy | create | |