Thomas Kluyver

Can you check `jupyter kernelspec list` to see if there's another kernel spec overriding the one you found?

@minrk could this be a result of trying to install the kernelspec as a data file in the Python package installation? I notice that it's using the new generic `python`...

@Daniel-M no worries, I was asking @minrk if this could be related to a new way kernel specs are being installed. I'm pretty sure it is , having thought about...

When you do `python2 -m ipykernel install --user`, does it tell you where it wrote to? If not, try with `--debug` and see if that does. I wonder if it's...

I wonder if there's something special binder does when building images that overrides the kernelspec file you created. @choldgraf @yuvipanda ?

If you want to use kernels from conda environments, you can install a package called something like nb_conda_kernels which provides kernels based on conda environments.

Or you can install a different kernelspec file for each environment (i.e. use names other than `python3`).

The first bit at least appears to be coming from ZMQ - @minrk , any ideas?

Not as far as I known. Would you like to work on it?

I believe the variable name `xxx_todo_changeme` comes from 2to3, not libmodernize, so we can't easily fix it.