These are chat archives for ipython/ipython

15th
Apr 2015
Brian E. Granger
@ellisonbg
Apr 15 2015 05:51 UTC
@takluyver about paths.py - I am not sure I understand what "not specific to ipython" means. Things in utils are specific to ipython in that ipython is the only project that does or should use these things.
Do you mean "could be useful to external project but we consider them to be private APIs so other external projects should never use them"?
I agree there is some difference, but I am not sure the difference is so clear
Also, I think we want to have a subpackage for all of the things like paths.py. Otherwise, the second there is anything else in that category, we will accidentatly put it into utils.
Thomas Kluyver
@takluyver
Apr 15 2015 12:02 UTC
well, we've had utils for years and it mostly has not got cluttered with IPython specific things (as in, things that only make sense to use in IPython)
If we want to put them in a subpackage, I would opt for core or maybe lib
but now that IPython is a much smaller project again, I don't see a problem with just putting public APIs like that in the IPython top level package.
Andreas Klostermann
@akloster
Apr 15 2015 14:34 UTC
Just asking: Has there been a new development with the aiozmq based kernel? I recently hacked an asyncio webserver into Blender, and ipython notebook support would be great...
Thomas Kluyver
@takluyver
Apr 15 2015 14:38 UTC
If so, no - feel free to take it and run with it, but be warned it is quite rough.
Andreas Klostermann
@akloster
Apr 15 2015 14:50 UTC
thank you
Jason Grout
@jasongrout
Apr 15 2015 17:47 UTC
@minrk - any hints on how to migrate kernels to the new jupyter_notebook?
Matthias Bussonnier
@Carreau
Apr 15 2015 17:51 UTC
they shoudl still work as is right now.
Mine still works/
do you mean kernelspec ? or actual imports ?
Jason Grout
@jasongrout
Apr 15 2015 17:52 UTC
Previously, the kernels were in ~/.ipython/kernels/
I don't think they are getting recognized anymore. Can I just move them to ~/.local/share/jupyter/kernels/ ?
Yes, I guess I mean the kernel specs
Min RK
@minrk
Apr 15 2015 18:01 UTC
It should be finding the IPython kernels while we haven't set up the migration script, yet.
Until we get the APIs set up, the new home is $(python -c 'from jupyter_core import paths; print(paths.jupyter_data_dir())')/kernels
Jason Grout
@jasongrout
Apr 15 2015 18:04 UTC
Thanks. Hey, I just tried using the kernelspec subcommand, but there was a python3-ism that gave a syntax error. Fix is here: jupyter/jupyter_client#3
Min RK
@minrk
Apr 15 2015 18:05 UTC
Looks like I did the shim for nbextensions, but not kernelspecs.
@jasongrout jupyter/jupyter_client#4
Jason Grout
@jasongrout
Apr 15 2015 18:08 UTC
Thanks!