Hi Derek,
> the framework. Though, if I understand correctly, Anaconda provides a
> framework version of the interpreter
> pythonw and a non-frameworked python?
This is right -- the GUI backends to matplotlib cause python to crash, but
not pythonw. This is annoying, since the two binaries
are equivalent under most other python installs. E.g. the mac system python
manpage reads:
To support multiple versions, the programs named python and pythonw now
just select the real version of Python to run, depending on various
set-
tings. (As of Python 2.5, python and pythonw are interchangeable; both
execute Python in the context of an application bundle, which means
they
have access to the Graphical User Interface; thus both can, when
properly
programmed, display windows, dialogs, etc.)
So people don't usually think to invoke different anaconda python commands,
leading to unexpected crashes (especially when using tools like pytest,
which invoke python, run a test that needs MPL, and crash).
This definitely seems like Anaconda's problem rather than matplotlib's (it
affects any program that tries to import Qt, e.g.)
chris
------------------------------------------------------------------------------
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
