This project has moved and is read-only. For the latest updates, please go here.

IPython fails to load in VS2013 CTP 5/PTVS 2.2

Mar 10, 2015 at 3:01 PM
Edited Mar 10, 2015 at 3:03 PM
Hi PTVS team,
I am running VS 2013 premium with CTP 5 update on a 64 bit win 8.1 system. I have installed Python 64-bit 2.7.9 (by hand using a combination of PIP and running PIP List I get:

backports.ssl-match-hostname (
certifi (14.5.14)
curses (2.2)
docutils (0.12)
ipython (3.0.0)
Jinja2 (2.7.3)
jsonschema (2.4.0)
lmfit (0.8.3)
lsqfit (6.0)
MarkupSafe (0.23)
matplotlib (1.4.3)
mistune (0.5)
mock (1.0.1)
nose (1.3.4)
numpy (1.9.2)
numpydoc (0.5)
pandas (0.15.2)
pip (6.0.8)
Pygments (2.0.2)
pyparsing (2.0.3)
pyreadline (2.0)
python-dateutil (2.4.1)
pytz (2014.10)
pywin32 (219)
pyzmq (14.5.0)
requests (2.5.3)
scipy (0.15.1)
setuptools (14.0)
six (1.9.0)
Sphinx (1.2.3)
tornado (4.1)
wheel (0.24.0)

Launching VS 2013 as administrator, PTVS connects, but IPython fails to load. Configuring the interactive window to run IPython is uneventful, on refresh of the interactive window I get:

Resetting execution engine
The Python REPL process has exited

I have IPython 3.0.0 installed (and it works fine in a "simple" cmd window, including matplotlib and pylab)

in the site-packages IPython folder there is no default configuration file

In the PTVSD folder I have:

There is no IPython REPL - is that correct?

Thinking this may be due to conflicts with win 8.1 etc. I set up a completely clean install using Hyper-V. Win 7 x64, VS2013, excel and word and ultraedit with Python 2.7.9 64 bit and get the same result - ie no IPython in the directory structure of PTVS, although it is present in the root directory of python itself.

At this stage, I would appreciate any insights about how to move forward and get this working.
Mar 10, 2015 at 5:00 PM
The file will be one directory higher than ptvsd - we have a bit of duplication there that we want to get rid of, but it's a bit too much work for us to do right now.

It's possible that IPython 3.0 has broken our support. Luckily, since it's entirely in Python code, you can debug it yourself and get moving that way. I'd suggest starting a python.exe, doing os.chdir into our install directory, then do import visualstudio_ipython_repl. If that fails, you'll have more information to go on (and I suspect we're simply importing something that's been removed). You can also modify that file while VS is running and hit the Reset button on the Interactive window to reload it, so you can experiment with that.

Otherwise, this is an important scenario for us, so we'll certainly look into it ourselves. You're welcome to help us out by telling us exactly what's wrong and how to fix it though :)
Mar 10, 2015 at 9:14 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.