IPython Notebook kernel crash on Win7x64

[jdfreder]

IPython Notebook kernel crash on Win7x64

Procedure:

1. Run ipython3 notebook
2. When the IPython dashboard rendered, I clicked the new notebook button.
3. When the notebook frontend rendered, a kernel crash dialog popped up and said the kernel would automatically restart. The automatic restart failed in addition to my attempt to manually restart the kernel.

System:

OS: Windows 7 Ultimate 64 bit
Environment: Python 3.3.2 32-bit
Browser: Mozilla Firefox 22.0
Installed Python Dependencies:
    nose
    pygments
    tornado
    pyzmq
    Jinja

Error message:

SyntaxError: invalid syntax
2013-08-07 13:32:16.908 [NotebookApp] KernelRestarter: restarting kernel (4/5)
WARNING:root:kernel 75a6a60d-e328-4a56-b19a-be90911baf71 restarted
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File ".\IPython\__init__.py", line 43, in <module>
    from .config.loader import Config
  File ".\IPython\config\__init__.py", line 16, in <module>
    from .application import *
  File ".\IPython\config\application.py", line 286
    print os.linesep.join(lines)
           ^
SyntaxError: invalid syntax
2013-08-07 13:32:20.112 [NotebookApp] WARNING | KernelRestarter: restart failed
2013-08-07 13:32:20.112 [NotebookApp] WARNING | Kernel 75a6a60d-e328-4a56-b19a-b
e90911baf71 died, removing from map.
ERROR:root:kernel 75a6a60d-e328-4a56-b19a-be90911baf71 restarted failed!

Looks like a similar problem was reported here: https://github.com/samueljohn/homebrew-python/issues/23

[minrk]

You don't have a proper install of IPython. This can happen if you have done python setup.py build with Python 2 prior to doing it with Python 3, which can skip the 2to3 pass.

[jdfreder]

Ahh, I just ran python setup.py insall develop

[minrk]

install develop doesn't make sense, and Python 3 doesn't support develop when 2to3 is required.

[jdfreder]

That's not cool, so I'll have to build every time I want to test my changes?

[jdfreder]

Thanks, running this fixed it

python setup.py build
python setup.py install

[minrk]

That's not cool, so I'll have to build every time I want to test my changes?

Yes, which only takes a second, because 2to3 doesn't re-run on files it has already processed.
This is one of the main reasons we want to drop 3.2 support and switch to a single codebase.

[Carreau]

@jdfreder, you should ping @bfroehle that IIRC have a run hook that run 2to3 on the fly.

[ivanov]

I recognized that error, because I've been running into this myself in the past couple of days :)

just want to chime in to say it's awesome that we're all testing on Python3 now!

[Carreau]

just want to chime in to say it's awesome that we're all testing on Python3 now!

Hopefully in a few hours we'll drop support for 2.6 also :-)

[jdfreder]

we want to drop 3.2 support and switch to a single codebase

&

we'll drop support for 2.6 also

We may drop both?

[Carreau]

We may drop both?

We will drop both. 2.6 for some exception syntax for example (IIRC), and 3.2 because it does not support unicode literals.

[ivanov]

@Carreau we're doing lab meeting now, if you're able to join