Hi Tommy,
Look inside the pyplot.py module. I don't have the code in front of me now, but
I guess it's a module that loads a bunch of other modules, and one of those
wants to use X11. This should not depend on whether the developers‘ tools are
present.
-michiel
On Jul 20, 2013, at 9:09 AM, Michiel de Hoon wrote:
>
> The MacOSX backend itself does not use X11. So I would suggest to check which
> modules get loaded when you import pyplot, and see which one of those causes
> X11 to open.
Thanks. How do I check which modules get loaded? When I import p
The MacOSX backend itself does not use X11. So I would suggest to check which
modules get loaded when you import pyplot, and see which one of those causes
X11 to open.
-Michiel
--
On Fri, Jul 19, 2013 4:14 PM EDT Tommy Grav wrote:
>I just installed matplotlib on a
On Jul 19, 2013, at 4:49 PM, Benjamin Root wrote:
> What does "print matplotlib.get_backend()" say?
'MacOSX'
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with applicati
What does "print matplotlib.get_backend()" say?
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose roo
I just installed matplotlib on a new MacBook Pro
ActivePython 2.7.2.5 (ActiveState Software Inc.) based on
Python 2.7.2 (default, Jun 24 2011, 12:20:15)
[GCC 4.2.1 (Apple Inc. build 5664)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> numpy.
