matplotlib-users Mailing List for matplotlib

On Jul 20, 2013, at 6:04 PM, Tommy Grav <tg...@ma...> wrote:

> On Jul 20, 2013, at 11:19 AM, Michiel de Hoon <mjl...@ya...> 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?

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 11:19 AM, Michiel de Hoon <mjl...@ya...> 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?

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 <mjl...@ya...> 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
>Mat...@li...
>https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Jul 20, 2013, at 9:09 AM, Michiel de Hoon <mjl...@ya...> 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

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 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.__version__
>'1.7.1'
>>> import matplotlib
>>> matplotlib.__version__
>'1.2.1'
>>> matplotlib.matplotlib_fname()
>'/Users/tgrav/.matplotlib/matplotlibrc'
>>> 
>
>That works fine. However, when I try to do
>
>import matplotlib.pyplot as plt
>
>it tries to open X11, which I have not installed and would like to 
>try to avoid. The matplotlibrc file has
>
>backend     : MacOSX 
>
>Anyone know why it is still trying to open X11 and how I can avoid that?
>
>
>------------------------------------------------------------------------------
>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
>Mat...@li...
>https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Jul 19, 2013, at 4:49 PM, Benjamin Root <ben...@ou...> wrote:

> What does "print matplotlib.get_backend()" say?

'MacOSX'