On 06/12/2010 08:12 PM, Michiel de Hoon wrote:
> So on Linux, show(block=True) blocks but show(block=False) doesn't? If
> matplotlib is in interactive mode, does show(block=True) still block? Because
> if matplotlib is in interactive mode, then the call to
> matplotlib.interactive(True) shouldn'
--- On Fri, 6/11/10, Eric Firing wrote:
> I agree that the difference in blocking behavior is still a
> problem. I think that what we should do for now, *if* multiple
> calls to show work on the Mac (which I can't easily test), is
> change the documentation to correspond to the present situation,
Something that I have noticed:
When using TkAgg (python 2.5, OSX/ppc, mpl 99.0), isinteractive() switches
from False to True after the first call to show() (see below). When I
switch back ends, e.g. to Qt4, this change does not happen until I do it
myself through ion(). This was reproduceable on
On 06/13/2010 07:39 AM, Daniel Welling wrote:
> Something that I have noticed:
> When using TkAgg (python 2.5, OSX/ppc, mpl 99.0), isinteractive()
> switches from False to True after the first call to show() (see below).
> When I switch back ends, e.g. to Qt4, this change does not happen until
> I
Hello,
I recently updated matplotlib using macports, and it broke my plotting
functions which plot date-value plots.
The reason was that my locale.getpreferredencoding() returned empty string
in
cbook.py.
changing the code to the following solved my problem
# On some systems, locale.getpreferre
On 06/13/2010 08:23 AM, Гузий Саша wrote:
> Hello,
>
> I recently updated matplotlib using macports, and it broke my plotting
> functions which plot date-value plots.
>
> The reason was that my locale.getpreferredencoding() returned empty
> string in
> cbook.py.
>
> changing the code to the followi
