[IPython-dev] Discovering kernels/profiles

[MinRK]

On Sun, Nov 10, 2013 at 2:19 AM, Matthias BUSSONNIER <
bussonniermatthias at gmail.com> wrote:

>
> Le 9 nov. 2013 à 22:49, Thomas Kluyver a écrit :
>
> > I'm starting to think about how newly installed kernels can be
> discovered by IPython, and the links between kernels and profiles.
> > ....
> >
> > Does this sound sensible?
>
> But other things might need to change when you change kernels. Like
>  syntax highlighting,
> execute_on_complete_block, logo in the notebook, default code_mirror_theme.
>

Yes, and we need to figure out how to address that without creating a
profile for each,
because we need to be able to use multiple kernel types with one server
instance,
which means one profile.



> So you actually do need to have a full config logic loading that change
> depending on the kernel.
> You cannot **just** create a profile on the fly.
>
> I think that the "include the names of kernels that don't yet have a
> matching profile"
> make no sense. Either the kernel is installed and ships with a
> default-profile (in whatever form)
> or it does not exist.
> Also I would be more in favor of a structure along :
>
> .ipython/profiles_default/
>         - config_*.json
>         - IJulia/
>                 -config.json
>                 -notebook-config.json
>         - IHaskell/
>                 -config.json
>                 -notebook-config.json
>         - IRuby/
>                 -config.json
>                 -notebook-config.json
>         ...
> .ipython/profiles_foo/
>         - config_*.json
>         - IJulia/
>                 -config.json
>                 -notebook-config.json
>         - IHaskell/
>                 -config.json
>                 -notebook-config.json
>         - IRuby/
>                 -config.json
>                 -notebook-config.json
>         ...
>
> --
> M
>
>
>
>
> >
> > Then there's the question of how to handle multiple kernels sharing a
> profile. We could allow a general mechanism for this, or special case the
> Python 2/3 kernels, or just drop the possibility and force the Python
> kernels to use separate profiles.
> >
> > Thanks,
> > Thomas
> > _______________________________________________
> > IPython-dev mailing list
> > IPython-dev at scipy.org
> > http://mail.scipy.org/mailman/listinfo/ipython-dev
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20131110/f206a9fb/attachment.html>