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 Sat, Jul 20, 2013 9:16 AM EDT Tommy Grav wrote:
On Jul 20, 2013, at 9:09 AM, Michiel de Hoon <mjldehoon@...9...> 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 pyplot a window pops up that explains that X11 is no longer part of the Mac OS X distribution and the python shell exits to the prompt.
Also are there anything I need to do to make MacOSX available to matplotlib. I have installed XCode, but I notice that there is no longer a /Developer directory at the root level (all developer code resources are not part of XCode application). Could this be causing matplotlib to not find the MacOSX environment? Or am I missing a path or keyword in my bash environment perhaps?
Cheers
Tommy
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
matplotlib-users List Signup and Options
Ok, so with a long list of print statements I have tracked it down to
the statement
import matplotlib._png as _png
in image.py. So there seems to be a bad binding in the _png.so file. Is there
a way to figure out which bindings this file has?
···
On Jul 20, 2013, at 11:19 AM, Michiel de Hoon <mjldehoon@...9...> wrote:
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
otool -L path/to/_png.so
will "Display the names and version numbers of the shared libraries that the object file uses"
I think otool is installed when you install Xcode.
···
On Jul 20, 2013, at 6:04 PM, Tommy Grav <tgrav@...935...> wrote:
On Jul 20, 2013, at 11:19 AM, Michiel de Hoon <mjldehoon@...9...> wrote:
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
Ok, so with a long list of print statements I have tracked it down to
the statement
import matplotlib._png as _png
in image.py. So there seems to be a bad binding in the _png.so file. Is there
a way to figure out which bindings this file has?
Tommy,
Instead of a lot of print statements, you can use
python -v
if you are starting from a python interpreter.
-Sterling
···
On Jul 20, 2013, at 3:04PM, Tommy Grav wrote:
On Jul 20, 2013, at 11:19 AM, Michiel de Hoon <mjldehoon@...9...> wrote:
Ok, so with a long list of print statements I have tracked it down to
the statement
import matplotlib._png as _png
in image.py.