Export the ipynb to a directory outside of the current workspace, there wasn't any python code prompt at the start to change directory to the previous location of the .ipynb file.

[zhouwangyang]

Environment data

Version: 1.53.0-insider (user setup)
Commit: eaa959d34b863dec932077d94daece22504a396b
Date: 2021-01-18T05:13:25.733Z
Electron: 11.2.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.17134
anaconda: python 3.8.5(64 bit)
Build of python-insider: 2020.12.414227025
Build of Jupyter-insider: 2021.1.481581316-rc

Expected behaviour

1.Open the file in the browser, should get an initial cell added to change directory back to your workspace directory.
2.Open the file in the editor. There should be python code at the start to change directory to the previous location of the .ipynb file

Actual behaviour

1. Open the file in the browser, there did not get an initial cell added to change directory back to your workspace directory.
2. Open the file in the editor. There didn't python code at the start to change directory to the previous location of the .ipynb file

Steps to reproduce:

1. Run the code manualTestFile.py, and export the .ipynb to a directory outside of the current workspace(not default export path)
2. Open the file in the browser, you should get an initial cell added to change directory back to your workspace directory
3. Follow the previous steps for import, but import an ipynb that is located outside of your current workspace
   4.Open the file in the editor. There should be python code at the start to change directory to the previous location of the .ipynb file

[IanMatthewHuff]

@zhouwangyang Thanks for filing. Confirmed I'm not seeing the directory change on import.

[joyceerhl]

@IanMatthewHuff I was just debugging this. Provided that the python file we're running from is in the current workspace, this is working for me:

Open the file in the browser, there did not get an initial cell added to change directory back to your workspace directory.

Exporting and then opening in editor, I am also seeing this, not sure if this is what we are expecting to see?:

[greazer]

Regression perhaps, but we're unclear as to whether this needs to be fixed at all. We should change the test plan.

[greazer]

@zhouwangyang please reopen and provide any clarification if you're still seeing a problem.

[IanMatthewHuff]

I still repro this. But doesn't seem worthy of Sept consideration.

[DonJayamanne]

@IanMatthewHuff mentioned he could repro, as nothing has been done to fix this, I"m re-opening this issue.

[amunger]

When trying to reproduce this and looking at the code, it seems like all the limitations are by design:
export python script to notebook - only if current file exists on disk
export IW to notebook - no, no backing file
export notebook to python script - only when nbconvert is used as export method
import notebook as python script - only when nbconvert is used as export method

It would be a good idea to clarify the nbconvert limitation in the setting's description.

[amunger]

This feature has a few issues: the path format is broken for Windows, the path is incorrect for importing/exporting notebooks, and it's not implemented in non-nbconvert code-paths.
Looking at telemetry, this is a fairly low-use feature, and since this issue hasn't gotten much attention, we can probably just remove it.

[IanMatthewHuff]

Verified the deprecation: