#31228: py26-spyder and probably py-spyder installs unsupported ipython --------------------------------+------------------------------------------- Reporter: glazered@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.0.3 Keywords: spyder | Port: py26-spyder --------------------------------+------------------------------------------- Hello, According to the google code tracking system for spyder, the newest ipython (version 0.11) is not supported in spyder 2.0.12, and will not be fully supported until 2.2. Thus, on a new installation of py26-spyder (though I'd imagine anyone using the py27-spyder would also be effected), I receive the following error message: {{{ Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 /site-packages/spyderlib/widgets/externalshell/startup.py", line 181, in <module> import IPython.Shell ImportError: No module named Shell }}} This error is consistent with errors reported on other operating systems, according to this issue on the google code repository for spyderlib: http://code.google.com/p/spyderlib/issues/detail?id=723 This is unfortunate, as macports is the recommended way to install spyder, according to the google code repository, and from my own experiences, attempting to use homebrew, or compiling from source code. In order to work, ipython probably needs to be downgraded to 0.10, or some workaround using the beta source code of spyder 2.1, a development version of ipython 0.12, and a development version of a spyder plugin to connect the two. That's according to this blog from the developer, http://spyder-ide.blogspot.com/2011/08/preview-of-new-ipython-plugin- for.html Although a more recent post makes it appear as though development on that plugin has run into problems for the moment: http://spyder-ide.blogspot.com/2011/09/no-ipython-v011-support-in- spyders.html Thus, it seems that reverting to ipython 0.10 is the only solution for a workable spyder installation using macports. Has anyone else run into this? -- Ticket URL: <https://trac.macports.org/ticket/31228> MacPorts <http://www.macports.org/> Ports system for Mac OS