[IPython-user] [IPython-dev] A few notes on threading+GUI event loops in Ipython1

[Brian Granger]

>  >  I really wish the Twisted setuptools stuff was merged into trunk.  Do
>  >  you know if it will be in the upcoming twisted release?
>
>  I wish it was too. There don't seem to be many changes necessary (it's
>  a small diff for the branch), but the Twisted folks don't seem to be
>  motivated to make the merge. Perhaps if the IPython project presented
>  a good use case for it, we could convince them to make the merge. I
>  admit to being somewhat intimidated by the Twisted community and
>  mailing lists, but I'm willing to make the pitch to them, unless
>  there's a more connected Twisted guru amongst us who would like to do
>  it.

I will ping the Twisted list on this issue - they are about to release
a new version so the timing is good.

Brian

>
>
>  >
>  >  Cheers,
>  >
>  >  Brian
>  >
>  >
>  >
>  >  >
>  >  >
>  >  >  On Wed, Mar 19, 2008 at 8:21 PM, Brian Granger <ellisonbg.net@gmail.com> wrote:
>  >  >  > Hi,
>  >  >  >
>  >  >  >  With all the recent activity about GUi event loops + threading, I
>  >  >  >  figured I would jot down a few notes about the current state of GUI
>  >  >  >  event loop integration within IPython1.
>  >  >  >
>  >  >  >  1) The IPython1 engine/core can be run in two different modes: with
>  >  >  >  the twisted event loop (typically when it runs in another process) or
>  >  >  >  without it.
>  >  >  >
>  >  >  >  Thus, we will need to have support for GUI event loop integration that
>  >  >  >  works for both of these cases.
>  >  >  >
>  >  >  >  2)  If the twisted event loop is running, one option is to use one of
>  >  >  >  the twisted reactors like the wxreactor.
>  >  >  >
>  >  >  >  But, we will need to carefully study if these reactors really work
>  >  >  >  (there seems to be some evidence that there are problems).
>  >  >  >
>  >  >  >  3) The issue of threads in the IPython1 engine could get _very_
>  >  >  >  complicated (much more so even that the treading in ipython0).  Part
>  >  >  >  of the problem is that there is simply many more possibilities for how
>  >  >  >  the ipython1 engine can be run.  It is probably too early to tackle
>  >  >  >  these things, but we are getting close to needing to think about these
>  >  >  >  things.
>  >  >  >
>  >  >  >  Brian
>  >  >  >  _______________________________________________
>  >  >  >  IPython-dev mailing list
>  >  >  >  IPython-dev@scipy.org
>  >  >  >  http://lists.ipython.scipy.org/mailman/listinfo/ipython-dev
>  >  >  >
>  >  >
>  >
>