GeezerVison

…ython#111762)

Co-authored-by: Christian Walther <[email protected]>

…ython#111762)

Co-authored-by: Christian Walther <[email protected]>

The prelude restores the working directory as the first import root after the generated
script moved to /tmp. Its `else` branch inserted that directory even when Python had
deliberately left it out, defeating `-P` and `PYTHONSAFEPATH=1`, whose whole purpose is to
keep a writable directory off the import path.

Insert only when Python itself would have added a script directory. This matches how CPython
fixed `pdb` in python/cpython#111762 and how `ipykernel` and `pyright` resolved the same
problem. `sys.flags.safe_path` exists only on Python 3.11+, and this package supports 3.10,
so it is read through `getattr` with a `False` default; 3.10 has no safe path mode, so the
historical behaviour is preserved there.

Verified on Python 3.12 and 3.10:

- normal mode resolves the working directory, with existing PYTHONPATH entries behind it
- `-P` and `PYTHONSAFEPATH=1` no longer import from the working directory
- under safe path an existing PYTHONPATH entry still resolves, which is what Python does
  on its own
- Python 3.10 raises no AttributeError and keeps the normal-mode behaviour

Signed-off-by: danish9039 <[email protected]>

The prelude restores the working directory as the first import root after the generated
script moved to /tmp. Its `else` branch inserted that directory even when Python had
deliberately left it out, defeating `-P` and `PYTHONSAFEPATH=1`, whose whole purpose is to
keep a writable directory off the import path.

Insert only when Python itself would have added a script directory. This matches how CPython
fixed `pdb` in python/cpython#111762 and how `ipykernel` and `pyright` resolved the same
problem. `sys.flags.safe_path` exists only on Python 3.11+, and this package supports 3.10,
so it is read through `getattr` with a `False` default; 3.10 has no safe path mode, so the
historical behaviour is preserved there.

Verified on Python 3.12 and 3.10:

- normal mode resolves the working directory, with existing PYTHONPATH entries behind it
- `-P` and `PYTHONSAFEPATH=1` no longer import from the working directory
- under safe path an existing PYTHONPATH entry still resolves, which is what Python does
  on its own
- Python 3.10 raises no AttributeError and keeps the normal-mode behaviour

Signed-off-by: danish9039 <[email protected]>

The prelude restores the working directory as the first import root after the generated
script moved to /tmp. Its `else` branch inserted that directory even when Python had
deliberately left it out, defeating `-P` and `PYTHONSAFEPATH=1`, whose whole purpose is to
keep a writable directory off the import path.

Insert only when Python itself would have added a script directory. This matches how CPython
fixed `pdb` in python/cpython#111762 and how `ipykernel` and `pyright` resolved the same
problem. `sys.flags.safe_path` exists only on Python 3.11+, and this package supports 3.10,
so it is read through `getattr` with a `False` default; 3.10 has no safe path mode, so the
historical behaviour is preserved there.

Verified on Python 3.12 and 3.10:

- normal mode resolves the working directory, with existing PYTHONPATH entries behind it
- `-P` and `PYTHONSAFEPATH=1` no longer import from the working directory
- under safe path an existing PYTHONPATH entry still resolves, which is what Python does
  on its own
- Python 3.10 raises no AttributeError and keeps the normal-mode behaviour

Signed-off-by: danish9039 <[email protected]>

The prelude restores the working directory as the first import root after the generated
script moved to /tmp. Its `else` branch inserted that directory even when Python had
deliberately left it out, defeating `-P` and `PYTHONSAFEPATH=1`, whose whole purpose is to
keep a writable directory off the import path.

Insert only when Python itself would have added a script directory. This matches how CPython
fixed `pdb` in python/cpython#111762 and how `ipykernel` and `pyright` resolved the same
problem. `sys.flags.safe_path` exists only on Python 3.11+, and this package supports 3.10,
so it is read through `getattr` with a `False` default; 3.10 has no safe path mode, so the
historical behaviour is preserved there.

Verified on Python 3.12 and 3.10:

- normal mode resolves the working directory, with existing PYTHONPATH entries behind it
- `-P` and `PYTHONSAFEPATH=1` no longer import from the working directory
- under safe path an existing PYTHONPATH entry still resolves, which is what Python does
  on its own
- Python 3.10 raises no AttributeError and keeps the normal-mode behaviour

Signed-off-by: danish9039 <[email protected]>