[IPython-User] IPython included in Spyder v1.1.0
Mon Jun 21 03:27:29 CDT 2010
2010/6/18 Brian Granger <firstname.lastname@example.org>
> > Since v1.1.0 (which has recently reached Release Candidate 1), IPython
> > been integrated in the external console.
> > See here: http://spyderlib.googlegroups.com/web/ipython.png
> > and there: http://spyderlib.googlegroups.com/web/spyder_light.png
> > That is great news (and I hope that you will be excited by these
> > screenshots), and following this, Spyder v2.0 should be almost completely
> > based on IPython.
> > However, I still have some difficulties with IPython and I would really
> > appreciate some help to fix these bugs.
> > First of all, let me explain how it works. It's quite simple actually:
> > opening a Python interpreter in another process (QProcess) and this
> > interpreter executes a startup script which is here:
> > Now you can see that on Windows platforms, I'm forced to do ugly things
> > 1. fix the encoding which is not properly detected by Python in the
> > (I assume that it's a Python bug on Windows) and cause errors in
> Not sure about this one.
Maybe I wasn't clear: this is not an IPython issue at all. This is only
Python itself which is unable to detect stdout encoding when you are running
it in a separate process on Windows (e.g. the same issue occurs in emacs
running a Python shell on win32).
> > 2. change the sys.platform to anything but 'win32' to prevent IPython
> > doing this: (in IPython.genutils):
> > if sys.platform == 'win32' and readline.have_readline:
> > Term = IOTerm(cout=readline._outputfile,cerr=readline._outputfile)
> When we separate IPython into two processes, this logic will be
> modified, so this should be taken care of.
> > 3. add an environment variable (to the QProcess): TERM=emacs, to prevent
> > IPython from using msvcrt for the 'page_more' function implementation
> > because like emacs, Spyder doesn't like to be bypassed with
> > (see IPython.genutils.page_more definitions)
> The paging functionality will need to be refactored as well.
> For now, I think the hacks you are doing are probably the best way to
> go - at least until we get the two process stuff working in ipython
> itself this summer.
> > Worse, I found a very strange bug happening when opening a PyQt file
> > (QFileDialog.xxx) from a mainwindow -- e.g. when using the "save figure"
> > feature in a matplotlib figure: the GUI window freezes and switching back
> > the IPython console and pressing Enter will unblock it! This bug only
> > happens in a IPython session launched into a Python interpreter running
> in a
> > separate process (it does not happen in a simple Python interpreter
> > in a separate process).
> This probably has something to do with threading and event loops. You
> will definitely run into problems with the current designof ipython.
> Again, this is one of our top priorities that we are working on this
I really hoped that someone could think of a workaround for this one... I'm
quite stuck with it! :)
And I hope I won't have to wait until next IPython is released to fix this
bug: v0.10 has still not spread everywhere judging from users feedbacks.
> > Any help would be really appreciated!
> I would join the ipython-dev list to follow along as we progress this
> > Thanks,
> > Pierre
> > _______________________________________________
> > IPython-User mailing list
> > IPython-User@scipy.org
> > http://mail.scipy.org/mailman/listinfo/ipython-user
> Brian E. Granger, Ph.D.
> Assistant Professor of Physics
> Cal Poly State University, San Luis Obispo
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-User