vscode-jupyter: Native Notebooks - Python env for specific notebook is not remembered between sessions
Environment data
Version: 1.54.0-insider Commit: c47da720f351455681978a48edc4d9a0d095ea0e Date: 2021-02-24T12:22:35.736Z Electron: 11.3.0 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Darwin x64 20.3.0
- VS Code version: 1.54.0-insider
- Jupyter Extension version: v2021.3.593162453
- Python Extension version: v2021.3.593199507-dev
- OS and version: Darwin x64 20.3.0
- Python and/or Anaconda version: 3.8.1
- Type of virtual environment used: Conda
- Jupyter server running: Local
Expected behaviour
Specific conda env is remembered for .ipynb notebook between vscode restarts/reloads.
Actual behaviour
After every restart jupyter env reverts to the same conda env instead of the one set for current notebook. (same one every time, seems to be arbitrary, cant find anywhere this is defined).
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- Open my_notebook.ipynb
- reload window
- reopen my_notebook.ipynb
Logs
Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)
XXX
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 22 (14 by maintainers)
Yep the enotdir error was on: vscode-insiders: 1.55.0 python: v2021.3.636328865-dev jupyter: whichever vsix you just linked to
I’ll open new issues for the other two
Oh, so that should have the fixes. This is a new issue. I’ll create a new issue to track this ENOTDIR issue. Hope you dont mind it, its easier for us to track issues & work done/tobe done…
The fixes have landed, hopefully by the end of the day I’ll have a VSIX that you can test. I’m certain the new fixes will resolve your issue. Thanks for being patient.
Thanks for the logs, that helped, I can now replicate this as well.