-
Notifications
You must be signed in to change notification settings - Fork 335
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
Pick up kernelspecs from Jupyter directories #7
Comments
Which of these directories contains the kernelspecs? |
Multiples. It's the aggregation of all of them...
This is where I was bantering around with creating a simple wrapper script that would dump JSON to stdout with options we'd need from an alternate front end (like Hydrogen). The other alternative is to use what we've got and launch a python kernel just for Hydrogen that queries for this same information. It's either that or always searching particular paths. |
Gosh, that's ugly. I'd sure love a script that dumps JSON of all the kernels' info. |
Especially if that script worked across IPython and Jupyter. |
As the migration happens, IPython will just be one of the kernels for Jupyter. It's all the same team. When I get some free time after work, I'll start poking at what scripts could be useful for Hydrogen and Jupyter sidecar to call out to Jupyter for accurate information. |
What I mean is that I'd like this to still work for people who haven't Thanks! On Tue, May 19, 2015 at 4:51 PM Kyle Kelley notifications@github.com
|
Totally, I'll end up making a script that straddles both. Also, people are strange and install from master whether or not they're contributing to IPython/Jupyter. For this release it's a bit silly since it's mostly repackaging, but in previous versions it was a big delta. |
Awesome! For the moment I'm loading all kernels found in that list plus |
Done in #19. |
We'll need/want to search the new Jupyter paths as well for kernelspecs, just as in https://github.com/jupyter/jupyter_core/blob/master/jupyter_core/paths.py
This is for the future release of the Jupyter packages (but my and the rest of the IPython/Jupyter team's likeliness to use this package).
The text was updated successfully, but these errors were encountered: