Re: [Matplotlib-users] Building a binary package of matplotlib for OS-X

[Chris B. <Chr...@no...>]

Robert Kern wrote:
> Chris Barker wrote:
>> /usr/local/share/share/matplotlib/
>>
>> Note the double "share". I'm guessing that's the problem. 

> Use --install-data=/usr/local not /usr/local/share.

I didn't use --install-data anything! However, perhaps Py2App is.

> That's probably a 
> bug in matplotlib's setup.py somewhere. Pretty much every other package 
> expects --install-data=/usr/local/share or the like.

OK, then that would explain why Py2App is appending the extra "share". 
If the convention is to expect the "share" to be part of install-data, 
then it shouldn't be in the setup.py. However, I'm a little confused, as 
then the default would be to put it straight into the python root 
directory. With a straight "setup.py install" it now goes into:

/Library/...../Versions/2.4/share/matplotlib

so without the share, it would go into:

/Library/...../Versions/2.4/matplotlib

Which really doesn't seem right.

Maybe we could check for a "share" at the end of the given path and only 
add it if it's not there, but that really feels like a kludge.

> /usr/local/<etc> is the place to put these things. /System/Library/<etc> 
> is just inaccessible.

/System/Library is not good, but /Library/... is no less accessible. For 
another take:

Bob Ippolito wrote:

> Using data_files in this manner at all is usually the wrong thing to  
> do anyway.  Python packages should really put the files they need  
> into the package, not some semi-random location on the filesystem.

I tend to trust Bob in these matters. What is the logic for putting all 
that stuff outside of the package directory?

-Chris


-- 
Christopher Barker, Ph.D.
Oceanographer
                                     		
NOAA/OR&R/HAZMAT         (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...