-
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
Export uses the wrong interpreter to perform the export #1363
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
To be clear I don't mean install nbconvert into the user's python interpreter. Just check it first. That would have alleviated some of the issues on the other bug. Meaning do this:
|
related to microsoft/vscode-python#11396 |
I concur that the bug @IanMatthewHuff links above is core to this. My notebook fails with the messages above when I do the convert from within Code, but if I do it from the command line ('jupyter nbconvert XXX --to python'), it works fine. I'm using Conda, and the python interpreter for the extension, and the one for the notebook are both the same as the environment where I did this from the command line. |
Keeping this as must-fix since #710 is affecting many users. We closed that bug in the python repo prior to opening the jupyter repo. |
@greazer Hang on a second. I think that I already fixed this. Did this maybe get moved over from a completed pipeline? |
Yeah, this was fixed. It was this PR here in python: microsoft/vscode-python#14308 |
This doesn't seem to be fixed? Repro steps:
It uses the jupyter interpreter instead? Looking at the callstack, I'm not sure how it would ever get passed a candidate interpreter. |
@rchiodo are you using the command from the palette Jupyter: Export to HTML? Realized that I fixed this working with the ExportAs button, which does pass and use a candidate interpreter. Pretty sure that I didn't look at the palette commands. Will probably have to make an additional fix for them. |
I used the export button at the top of a native notebook. |
Validated. |
It defaults to using the 'jupyter interpreter' instead of using the user's interpreter. This makes it impossible for the user to diagnose errors as the errors don't match what their current interpreter might report.
See this issue:
#710
The text was updated successfully, but these errors were encountered: