Skip to content

proton: undo the effect of PYTHONSAFEPATH if any#9712

Open
Summertime wants to merge 2 commits intoValveSoftware:bleeding-edgefrom
Summertime:patch-2
Open

proton: undo the effect of PYTHONSAFEPATH if any#9712
Summertime wants to merge 2 commits intoValveSoftware:bleeding-edgefrom
Summertime:patch-2

Conversation

@Summertime
Copy link
Copy Markdown

@Summertime Summertime commented Apr 24, 2026

Usually not set system-wide, but should be: PYTHONSAFEPATH disables the ability to import from the current working directory.

with PYTHONSAFEPATH enabled:

['/var/lib/...', ...] becomes [PROTON_DIR, '/var/lib/...', ...]

without PYTHONSAFEPATH enabled:

[PROTON_DIR, '/var/lib/...', ...] becomes [PROTON_DIR, PROTON_DIR, '/var/lib/...', ...]

The double entry should have the same effect as a single entry (enabling relative imports)


The relevant pieces in play:

https://docs.python.org/3/using/cmdline.html#envvar-PYTHONSAFEPATH

https://docs.python.org/3/library/sys.html#sys.path

https://docs.python.org/3/reference/datamodel.html#module.__file__


Testing done: in a session with PYTHONSAFEPATH=1 set in my ~/.config/environment.d folder: Games don't launch sometimes. If I add these lines, they launch. Have not tried to see if it causes any negative changes in a environment without PYTHONSAFEPATH set

Proton CI Bot and others added 2 commits April 24, 2026 16:02
with PYTHONSAFEPATH enabled:

`['/var/lib/...', ...]` becomes `[PROTON_DIR, '/var/lib/...', ...]`

without PYTHONSAFEPATH enabled:

`[PROTON_DIR, '/var/lib/...', ...]` becomes `[PROTON_DIR, PROTON_DIR, '/var/lib/...', ...]`

The double entry should have the same effect as a single entry (enabling relative imports)

The relevant pieces in play:

https://docs.python.org/3/using/cmdline.html#envvar-PYTHONSAFEPATH

https://docs.python.org/3/library/sys.html#sys.path

https://docs.python.org/3/reference/datamodel.html#module.__file__
@Plagman Plagman force-pushed the bleeding-edge branch 28 times, most recently from 6c571a9 to d066205 Compare April 30, 2026 10:57
@Plagman Plagman force-pushed the bleeding-edge branch 10 times, most recently from 4146afd to 3c93b11 Compare May 1, 2026 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant