Open dschien opened 7 years ago
Are you running multiple notebook servers or have any runtime notebook server metadata lurking in your home directory? jupyter --paths
can tell you what runtime directories to check. The files would look like:
-rw-r--r-- 1 parente staff 274 Feb 18 12:52 nbserver-41581.json
The reason I ask is because the extension uses the first one of those config files it finds to determine what root path to use for imports. It's flaky and should at least be written up as a release note here in the README.
Also, you might want to check out https://github.com/ipython/ipynb which has a different implementation of the importing feature and isn't in incubator.
Thanks for the reply. I did have a whole bunch of nbserver-* files. I removed those but without any effect on CMS.
Thanks for the pointer to the ipynb package. That will allow me to continue with my project. Still a real shame the CMS broke on my system... anything else I can do to diagnose?
The nbserver files have been the culprit in the past. Did you restart the live notebook server after the cleanup?
I'll try to reproduce here with the latest version.
Restarted but without effect. Thanks
Hi
The most recent version of CMS seems broken.
I fail to import notebooks.
I have a small notebook
mylib.ipynb
And a notebook importing:
When running this, I get
OSX
Pristine virtual env Python 3.6.1
CMS installed according to instructions
Dependency versions: