-
Notifications
You must be signed in to change notification settings - Fork 9
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
No script folder generated by nbautoexport #70
Comments
Hi @Ziemersky, thank you for trying out nbautoexport! After running |
Hi Jay, thanks for the quick response! |
@Ziemersky can you share the output of the following commands:
And then also run the jupyter notebook server, open a notebook, explicitly save the notebook, and share the logs that the notebook server prints out when doing that? It should mention the script exports if it is working. |
@pjbull since the commands you mentioned throw an error of the following kind:
I assume you mean the For
and for
After starting the server and opening a file called "Glowplug_Temperature_normalized.ipynb", I pressed the "save" button. The output is:
It does not mention the script exports. |
Okay I figured it out.
and uncommented line 536 Turned out the path in the code snippet above is wrong. "chrome.exe" lies in |
Great! Glad we were able to help you resolve it. It's helpful to know about runtime errors in |
Description
Package generates .nbautoinstall file in the intended folder, but no 'script' folder, nor scripts are generated.
What I Did
I installed the package following the installation guide using the Anaconda 3 Prompt and the
conda install nbautoexport
command. Then I rannbautoexport install
and specified the folder directory vianbautoexport configure "path"
.The .nbautoexport file got generated and looks like this:
After running Jupyter Notebook (Versions: jupyter core: 4.7.1, jupyter-notebook : 6.3.0) and saving some of my .ipynb files, no 'script' folder was generated.
Since I am by no means an expert, let me know if I made an obvious mistake.
The text was updated successfully, but these errors were encountered: