Closed xncbf closed 19 hours ago
cc @gaogaotiantian
How did you run test_safe_path
with PYTHONSAFEPATH = 1
? It should be skipped (not that it's what I had in mind when I wrote the test).
@unittest.skipIf(sys.flags.safe_path,
'PYTHONSAFEPATH changes default sys.path')
def _run_pdb(self, pdb_args, commands,
expected_returncode=0,
extra_env=None):
./python.exe -m test test_pdb
./python.exe -m test test_pdb --forever
The above command fails when executed after the build. No other preliminary work is needed.
Are you able to repro this with
./python.exe -m test test_pdb -m test_safe_path
Can you copy/paste the full output? Is it because of mac that the test actually ran?
Closing as cannot reproduce
since the OP did not reply for a while.
Bug report
Bug description:
Issue: The test_safe_path function in test_pdb.py is failing. When PYTHONSAFEPATH is set to '1', sys.path[0] still includes the current working directory, which is unexpected.
Steps to Reproduce:
Expected Behavior: When PYTHONSAFEPATH is set to '1', sys.path[0] should not include the current working directory.
Actual Behavior: sys.path[0] includes the current working directory, and there's an unexpected $PYTHONPATH appended to the path.
Environment:
121724
CPython versions tested on:
CPython main branch
Operating systems tested on:
macOS