Open erlend-aasland opened 5 months ago
cc. @serhiy-storchaka
Most of these functions (especially implemented as macros) are thin wrappers around functions with richer interface, so it is not practical to repeat all tests for all functions. We only need to add comprehensive tests for base functions, and simpler tests for derived functions.
Some functions are implemented as macros, but also as real functions. It would be nice to test both implementations (only simple tests are needed).
The test_run_fileexflags
test that was added in #117982 sometimes crashes on LTO+PGO buildbots, see for example:
Do you want to look into this?
Functional tests for the
PyEval_Run
family of the C API lack tests. Discovered in the discussions of PR #116637.PyRun_AnyFile
(may be a macro)PyRun_AnyFileEx
(may be a macro)PyRun_AnyFileExFlags
PyRun_AnyFileFlags
(may be a macro)PyRun_File
(may be a macro)PyRun_FileEx
(may be a macro)PyRun_FileFlags
(may be a macro)PyRun_InteractiveLoop
(may be a macro)PyRun_InteractiveLoopFlags
PyRun_InteractiveOne
(may be a macro)PyRun_InteractiveOneFlags
PyRun_InteractiveOneObject
PyRun_SimpleFile
(may be a macro)PyRun_SimpleFileEx
(may be a macro)PyRun_SimpleFileExFlags
PyRun_SimpleString
(may be a macro)PyRun_SimpleStringFlags
PyRun_String
(may be a macro)Linked PRs