-
-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Respect sys.flags.safe_path #1311
Comments
I doubt this is the location that adds the problematic sys.path entry as this should be used only when building ipykernel wheels. |
Updating the kernel launch config file to pass this flag (or set a global configuration file with the proper configuration works:
or config file with:
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the following line, the script directory path is added even if Python was run with
sys.flags.safe_path
(most often by setting the env var PYTHONSAFEPATH=1).ipykernel/hatch_build.py
Line 15 in b11d42c
Not having the ability to set safe path causes problems when there are sibling Python files with names that clash with installed Python modules.
Thanks to @DonJayamanne for helping find the root cause in microsoft/vscode-jupyter#16235.
The text was updated successfully, but these errors were encountered: