Skip to content

Fix init_path ignoring CWD when -P used in script shebang (#15214)#15262

Open
frenzymadness wants to merge 1 commit into
ipython:mainfrom
frenzymadness:fix_cwd
Open

Fix init_path ignoring CWD when -P used in script shebang (#15214)#15262
frenzymadness wants to merge 1 commit into
ipython:mainfrom
frenzymadness:fix_cwd

Conversation

@frenzymadness

Copy link
Copy Markdown
Contributor

When Python is invoked as a script with -P in the shebang, sys.flags.safe_path is set but -P only excludes the script's directory from sys.path, not CWD. The previous fix in 9.7 treated safe_path as a blanket signal to skip adding CWD.

Now init_path only honors safe_path when Python was invoked as a module (-m) or with -c, which is when -P actually excludes the current working directory.

Fixes: #15214

)

When Python is invoked as a script with -P in the shebang,
sys.flags.safe_path is set but -P only excludes the
script's directory from sys.path, not CWD. The previous fix in 9.7 treated
safe_path as a blanket signal to skip adding CWD.

Now init_path only honors safe_path when Python was invoked as a module
(-m) or with -c, which is when -P actually excludes the current working
directory.
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.

CWD is not in sys.path when "-P" is used

1 participant