-
Notifications
You must be signed in to change notification settings - Fork 300
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
Jupyter notebook current working directory is the $HOME directory, rather than the file directory or the workspace directory. #16430
Comments
Thank you for reporting this issue and sorry you are running into this. Please can you share the top part of the logs. |
Looks like you still have the 2024.11.0 version installed, you might want to re-load VS Code (or just re-start the extensions) if you did install 2025.1.0. |
Here is the top part of the logs Show Logs
|
And here's the logs after updating to 2025.1.0 |
Applies To
What happened?
Recently my notebooks using relative imports stopped working. When investigating why, I found that the notebooks were working inside my home directory, not the file directory or workspace directory (the same, in this case). These same imports worked a few weeks prior to June 2024
What I expected to happen:
Relative imports should work without modifying the path when both the notebook and the module being imported are in the same directory, and that directory is also the workspace root.
What actually happened:
Relative imports failed due to not finding the module
VS Code Version
Version: 1.96.2 (user setup) Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f Date: 2024-12-19T10:22:47.216Z Electron: 32.2.6 ElectronBuildId: 10629634 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Windows_NT x64 10.0.22635
Jupyter Extension Version
2025.1.0
Jupyter logs
Coding Language and Runtime Version
Python v3.11
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote
The text was updated successfully, but these errors were encountered: