Another try at interactive gui thread

John, this looks like an much improved interactive.py, is

    > it OK to use it to replace interactive.py in cvs, and if so
    > should the '-pylab' option be left as it is or removed to
    > be compatible with the current interactive.py?

Hey Steve,

I probably just forgot to update interactive.py last time Fernando
sent it to me. Feel free to do update interactive.py and its
interface and command line args (eg, pylab or not) as you see fit.
Just update the changelog so I can include them in the next release
notes.

After you're done, you may want to take a look at interactive.html
and/or \section{Interactive} of the user's guide, and make updates as
you see fit.

Thanks!
JDH

I replaced examples/interactive.py with Fernando's updated version
(adding a comment that gtk.main runs in the main thread and replacing
gtk.timeout_add with gobject.timeout_add).

I looked at interactive.html.template and user_guide.tex and saw a
reference to ipython, but no mention of interactive.py, so it does not
look like they need updating. I seem to recall interactive.py being
mentioned in the docs in the past, but they must have been changed since
then.

Steve

···

On Thu, 2005-01-27 at 11:43 -0600, John Hunter wrote:

I probably just forgot to update interactive.py last time Fernando
sent it to me. Feel free to do update interactive.py and its
interface and command line args (eg, pylab or not) as you see fit.
Just update the changelog so I can include them in the next release
notes.

After you're done, you may want to take a look at interactive.html
and/or \section{Interactive} of the user's guide, and make updates as
you see fit.