Latest IPython Won't Start

[Dave Hirschfeld]

I've got the latest IPythond when I try to open an IPython console it doesn't open and I get the following traceback in the internal console: an

Spyder 2.2.0rc internal shell on Python 2.7.2 32bits [Windows]

Inspect Spyder internals:

  spy.app, spy.window, dir(spy)

>>> {u'hb_port': 54577,

 u'iopub_port': 55614,

 u'ip': u'127.0.0.1',

 u'key': u'0b753489-46be-4831-87e0-25d9a662d16c',

 u'shell_port': 52005,

 u'stdin_port': 65409,

 u'transport': u'tcp'}

Traceback (most recent call last):

  File "C:\dev\code\spyderlib\spyderlib\plugins\externalconsole.py", line 869, in <lambda>

    cf, kernel_widget=shellwidget))

  File "C:\dev\code\spyderlib\spyderlib\plugins\externalconsole.py", line 947, in create_ipyclient

    self.main.ipyconsole.new_client(connection_file, id(kernel_widget))

  File "C:\dev\code\spyderlib\spyderlib\plugins\ipythonconsole.py", line 878, in new_client

    self.register_client(cf, kernel_widget_id, client_name)

  File "C:\dev\code\spyderlib\spyderlib\plugins\ipythonconsole.py", line 947, in register_client

    config=self.ipywidget_config())

  File "C:\dev\code\spyderlib\spyderlib\plugins\ipythonconsole.py", line 813, in new_ipywidget

    widget.kernel_manager = kernel_manager

  File "c:\dev\code\ipython\IPython\frontend\qt\base_frontend_mixin.py", line 81, in kernel_manager

    kernel_manager.kernel_restarted.connect(self._handle_kernel_restarted)

AttributeError: 'QtKernelManager' object has no attribute 'kernel_restarted'

In [3]: print sys_info()

{'commit_hash': 'c3a9044',

'commit_source': 'repository',

'default_encoding': 'cp1252',

'ipython_path': 'c:\\dev\\code\\ipython\\IPython',

'ipython_version': '1.0.dev',

'os_name': 'nt',

'platform': 'Windows-7-6.1.7601-SP1',

'sys_executable': 'C:\\dev\\bin\\Python27\\python.exe',

'sys_platform': 'win32',

'sys_version': '2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)]'}

-Dave

[Jed Ludlow]

Yup, I can reproduce this. It looks like there have been some major changes in the last few days to IPython internals related to kernel managers. See here:

https://github.com/ipython/ipython/pull/3011

Yikes. Have to decide how to react to this. Kind of lousy timing now that 2.2 is just about ready.... 

[Carlos Córdoba]

I was following that PR quite closely and unfortunately it represents a major API breakage which will force us to rewrite a lot of the logic for connecting, interrupting and restarting kernels that we already have.

The best thing we can do is leave things as they are now, and make the necessary changes for 2.3, because we won't be able to support IPython 0.13 and 1.0dev at the same time.

So 2.2 will be meant to work with the current stable IPython release (0.13) and 2.3 with the next one (1.0).

Cheers,
Carlos

El 26/04/13 11:12, Jed Ludlow escribió:

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+...@googlegroups.com.
To post to this group, send email to spyd...@googlegroups.com.
Visit this group at http://groups.google.com/group/spyderlib?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jed Ludlow]

On Fri, Apr 26, 2013 at 10:23 AM, Carlos Córdoba <ccord...@gmail.com> wrote:

I was following that PR quite closely and unfortunately it represents a major API breakage which will force us to rewrite a lot of the logic for connecting, interrupting and restarting kernels that we already have.

The best thing we can do is leave things as they are now, and make the necessary changes for 2.3, because we won't be able to support IPython 0.13 and 1.0dev at the same time.

So 2.2 will be meant to work with the current stable IPython release (0.13) and 2.3 with the next one (1.0).

I can support that approach.

[Carlos Córdoba]

Do you mean trying to make 0.13 and 1.0 work at the same time?

El 26/04/13 12:07, Jed Ludlow escribió:

[Jed Ludlow]

On Fri, Apr 26, 2013 at 11:53 AM, Carlos Córdoba <ccord...@gmail.com> wrote:

Do you mean trying to make 0.13 and 1.0 work at the same time?

No, I mean supporting only IPython 0.13 for now and waiting until 2.3 to support IPython 1.0.

[Tim Michelsen]

> Do you mean trying to make 0.13 and 1.0 work at the same time?
>
>
> No, I mean supporting only IPython 0.13 for now and waiting until 2.3 to
> support IPython 1.0.

This may be related:
http://code.google.com/p/spyderlib/issues/detail?id=1374

[Carlos Córdoba]

It is the same, yeah.

El 30/04/13 16:38, Tim Michelsen escribió:

[Tim Michelsen]

> It is the same, yeah.

So I need to downgrade IPython?

[Carlos Córdoba]

Yep, sorry. After 2.2 is (finally) released, I'll start to work on this one.

El 30/04/13 16:41, Tim Michelsen escribió:

[Steve]

When you say ipython 0.13 does that include 0.13.1?

[Carlos Córdoba]

Yep, up to 0.13.2.

El 30/04/13 16:46, Steve escribió:

[Tim Michelsen]

> Yep, up to 0.13.2.

> El 30/04/13 16:46, Steve escribi�:

>> When you say ipython 0.13 does that include 0.13.1?
>>
>> On Tuesday, April 30, 2013 4:41:02 PM UTC-5, Timmie wrote:
>>
>> > It is the same, yeah.
>> So I need to downgrade IPython?

what about a fall-back mode?
so that apyder can start but would not use the ipython console, just the
traditional one?

[Sylvain Corlay]

You can always use the regular console widget. 

On Tuesday, April 30, 2013 7:26:01 PM UTC-4, Timmie wrote:

> Yep, up to 0.13.2.

> El 30/04/13 16:46, Steve escribi�:

[Pierre Raybaut]

Do you mean that Spyder crashes with IPython >= 1.0?

Then, for v2.2, we should handle a range of valid versions for
IPython: 0.12 <= valid version <= 0.13.2.

-Pierre

Le 1 mai 2013 à 01:26, Tim Michelsen <timmic...@gmx-topmail.de> a écrit :

>> Yep, up to 0.13.2.
>

>> El 30/04/13 16:46, Steve escribió:

>>> When you say ipython 0.13 does that include 0.13.1?
>>>
>>> On Tuesday, April 30, 2013 4:41:02 PM UTC-5, Timmie wrote:
>>>
>>>> It is the same, yeah.
>>> So I need to downgrade IPython?
> what about a fall-back mode?
> so that apyder can start but would not use the ipython console, just the
> traditional one?
>

[Dave Hirschfeld]

On Wednesday, May 1, 2013 9:20:46 AM UTC+1, Pierre Raybaut wrote:

Do you mean that Spyder crashes with IPython >= 1.0?

Then, for v2.2, we should handle a range of valid versions for
IPython: 0.12 <= valid version <= 0.13.2.

-Pierre

Le 1 mai 2013 à 01:26, Tim Michelsen <timmic...@gmx-topmail.de> a écrit :

>> Yep, up to 0.13.2.
>
>> El 30/04/13 16:46, Steve escribió:
>>> When you say ipython 0.13 does that include 0.13.1?
>>>
>>> On Tuesday, April 30, 2013 4:41:02 PM UTC-5, Timmie wrote:
>>>
>>>> It is the same, yeah.
>>>    So I need to downgrade IPython?
> what about a fall-back mode?
> so that apyder can start but would not use the ipython console, just the
> traditional one?
>

Yep, the situation has gotten worse in that spyder will no longer start (at least the bootstrap script anyway):

C:\dev\code\spyderlib>bootstrap.py

Executing Spyder from source checkout

Revision 79a7f082e808+:2753+, Branch: default

01. Patched sys.path with C:\dev\code\spyderlib

02. No PySide detected, using PyQt4 if available

C:\dev\bin\Python27\lib\site-packages\pygments\plugin.py:39: UserWarning: Module argparse was already imported from C:\dev\bin\Python27\lib\argparse.pyc, but c:\dev\bin\python27\lib\site-packages is being added to sys.path

  import pkg_resources

C:\dev\bin\Python27\lib\site-packages\pygments\plugin.py:39: UserWarning: Module rope was already imported from C:\dev\code\spyderlib\rope\__init__.pyc, but c:\dev\bin\python27\lib\site-packages is being added to sys.path

  import pkg_resources

Traceback (most recent call last):

  File "C:\dev\code\spyderlib\bootstrap.py", line 77, in <module>

    from spyderlib import spyder

  File "C:\dev\code\spyderlib\spyderlib\spyder.py", line 108, in <module>

    from spyderlib.plugins.ipythonconsole import IPythonConsole

  File "C:\dev\code\spyderlib\spyderlib\plugins\ipythonconsole.py", line 31, in <module>

    from IPython.frontend.qt.kernelmanager import QtKernelManager

ImportError: No module named kernelmanager

C:\dev\code\spyderlib>

Reverting ipython to 251778c7e4cd3bcdd90eaecf9fa554e4041bd6da will still work with spyder:

i.e. in the ipython repository enter at the command line:

git checkout 251778c7e4cd3bcdd90eaecf9fa554e4041bd6da

python setupegg.py develop

HTH,

Dave

 

[Pierre Raybaut]

In the meantime, because IPython 1.0 won't be officially supported by Spyder 2.2, I've implemented the supported IPython versions like this: >=0.13 and <1.0.

No error should now be produced with IPython 1.0 but the IPython console plugin should be disabled.

-Pierre

2013/5/1 Pierre Raybaut <pierre....@gmail.com>

[Tim Michelsen]

> In the meantime, because IPython 1.0 won't be officially supported by
> Spyder 2.2, I've implemented the supported IPython versions like this:
>>=0.13 and <1.0.

> No error should now be produced with IPython 1.0 but the IPython console
> plugin should be disabled.

Confirmed:
http://code.google.com/p/spyderlib/issues/detail?id=1374

A suggestion:
issue a a warning on the commandline in case the IPython 1.0 is
installed an therefore the IPython console plugin disabled.

This way, you may avoid getting tons of issue entries or questions on
the list.

I do not know the release plans for IPY 1.0.

The fix from Pierre will be available in the next spyder package on the PPA.

Cheers,
Timmie