I am having problems with running the IPython shell from the Sublime REPL package.
Here is what I get:
C:\\Anaconda\\lib\\site-packages\\IPython\\c
With the release of IPython 4.0, the structure has completely changed, and is now implemented as a kernel for the Jupyter core, which is capable of running IPython-like sessions using many different languages other than Python. IPython is still the "reference implementation", however.
With these changes, the internal API has also changed quite a bit, and some parts have been moved/renamed or just aren't there at all. I've put together complete instructions on updating SublimeREPL for IPython 4 as a gist on Github, but I'll go over the key parts here.
The first thing you need to do is make sure you have all the components of IPython and Jupyter, as it's been split up from one monolithic packages to quite a number of smaller ones. Run
[sudo] pip install -U ipython jupyter
from the command line to get all the pieces - no compiler should be necessary. sudo
is in case you're on a Unix/Linux system and need admin access, and the -U
flag means the same thing as --upgrade
.
Once that's done, open Sublime and select Preferences → Browse Packages…
to open your Packages
folder in your operating system's file browser application (Finder, Windows Explorer, Nautilus, etc.). Open the SublimeREPL
folder, then config
, then Python
, then open ipy_repl.py
in Sublime. Delete its entire contents, and replace it with the file included in the gist link above (click here for the raw copy-and-paste version).
Save ipy_repl.py
with the new contents, and that should be it! You can now open the IPython REPL in the usual way, and you should see:
Jupyter Console 4.0.2
[ZMQTerminalIPythonApp] Loading IPython extension: storemagic
In [1]:
If you'd like to get rid of the [ZMQTerminalIPythonApp]
message, read through the instructions in the gist. However, the message is harmless, so you can safely ignore it if you want.
Good luck!
NOTE: These changes have been submitted to the main SublimeREPL project as pull requests, but seeing as the author hasn't been working on the plugin for some time, it may be a while before it's part of the main branch.