Re: [matplotlib-devel] GTK threading

[Fernando P. <Fer...@co...>]

Baptiste Carvello wrote:
> Hi,
>=20
> Steve Chaplin a =E9crit :

>>When thinking about using threads for interactive mode I had been
>>assuming people using the interactive mode would be using the pylab
>>interface, does anyone use the matplotlib class interface in interactiv=
e
>>mode?
>>
>=20
> I sometimes do.

Agreed.

One should also be able to execute interactively large scripts which may =
have=20
  been written to the OO interface.  I know that I routinely test 10k LOC=
=20
modules from within ipython (though not matplotlib based).  It would be I=
MHO=20
poor design to put all sorts of special-case warnings, where certain feat=
ures=20
of matplotlib would only be available in certain ways of using it.  Speci=
al=20
cases lead to madness...

Note that I haven't followed the details close enough to vouch for any=20
particular approach.  I just would like to see any solution implemented t=
o be=20
as clean and general as possible.  As far as users are concerned, these=20
details should be, where possible, totally irrelevant (internal implement=
ation=20
only).  As a reference, ipython tries mightily hard to make sure that _an=
y_=20
code which can be executed at a system command line as 'python foo.py'=20
produces identical behavior at an ipython prompt via 'run foo'.  There ar=
e=20
special options to 'run' for modifying this, but the default attempts to=20
emulate python very faitfully, just with better tracebacks, debug support=
,=20
etc.  And I consider deviations from this bevavior as bugs.  It's not 100=
%=20
perfect, but it really works fairly well in most cases.

Regards,

f