Conversation
IPython/utils/io.py
Outdated
There was a problem hiding this comment.
these lines were just a way for me to get vim to import IPython, but it was a kludge done without much thought. There's likely something else that should be done here, so please let me know what that should be
There was a problem hiding this comment.
Do you have to do this with all of them, or a subset? I realize that sys.stdin can sometimes be None, for example.
An alternative is to assign appropriate streams to sys.stdin/out/err prior to importing IPython things, but we should probably handle this gracefully.
There was a problem hiding this comment.
according to python docs, sys.stderr and sys.stdout are only required to have write() methods, but I've monkeypatched vim's stdout and stderr to fix this. Vim actually added flush() in their trunk
|
@ivanov, this is a bit too dangerous to merge this close to release, but it's very cool! I just saw the demo video, and it's awesome. We'll cut 0.11 without this, and can then merge it with plenty of time to deal with any possible problems before 0.12. Thanks! |
|
now with no changes to IPython trunk! 0.11? :) |
Two-way vim-ipython integration.
Two-way vim-ipython integration.
3 participants
here's a new and improved way of getting vim and ipython to talk to each other. Thanks to @minrk for guiding me through the protocol.
I also made a little demo of these new capabilities which you might be interested in checking out here: http://www.pirsquared.org/vim-ipython/
Others want to join in the fun in improving ipy.vim can do so here: http://github.com/ivanov/vim-ipython