that doesn't make much sense and there are necessary uses for eval() /exec(), mostly for dynamic creation of code: For example here's Python dataclasses in the

that doesn't make much sense and there are necessary uses for eval() /exec(), mostly for dynamic creation of code: For example here's Python dataclasses in the standard library using exec() to create the `__init__` and other methods that go on your dataclass: https://github.com/python/cpython/blob/main/Lib/dataclasses.py#L451 https://github.com/python/cpython/blob/main/Lib/dataclasses.... Here's Pydantic using it for a jupyter notebook check: https://github.com/pydantic/pydantic/blob/594effa279668bd955e98f1cd5c036b37d3bbd40/pydantic/_internal/_validation_functions.py#L150 https://github.com/pydantic/pydantic/blob/594effa279668bd955... here's Pytest using it to rewrite modules so that functions like assert etc. are instrumented by pytest: https://github.com/pytest-dev/pytest/blob/eca93db05b6c5ec1012f7a3e6590f316729ac243/src/_pytest/assertion/rewrite.py#L168 https://github.com/pytest-dev/pytest/blob/eca93db05b6c5ec101... Here's the decorator module using it (as is the only way to do this in Python) to create a signature matching decorator for an arbitrary function: https://github.com/micheles/decorator/blob/ad013a2c1ad7969963acf3dea948632be387f5a0/src/decorator.py#L160 https://github.com/micheles/decorator/blob/ad013a2c1ad796996... All of these libraries are completely secure as eval/exec are used with code fragments that are generated by the libraries, not based on untrusted input. eval() /exec() are not running executable files, just Python code, the same way all the rest of the package is already doing.