matplotlib-devel Mailing List for matplotlib

On 9-Mar-10, at 2:24 AM, Tom Loredo wrote:

> I've been experimenting with SVN checkouts of numpy and scipy,
> and found they are not compatible with mpl-0.99.1.  The
> problem is that the numpy version number for recent checkouts
> is 2.0.x (2.0.0.dev8289 for the version I'm currently using),
> but mpl's numpy version checking (on the 1st two digits) isn't
> quite smart enough to know that 2.0 > 1.1.

I ran into this too, it's fixed in SVN.

David

Hi folks-

I've been experimenting with SVN checkouts of numpy and scipy,
and found they are not compatible with mpl-0.99.1.  The
problem is that the numpy version number for recent checkouts
is 2.0.x (2.0.0.dev8289 for the version I'm currently using),
but mpl's numpy version checking (on the 1st two digits) isn't
quite smart enough to know that 2.0 > 1.1.  It's easy enough
to fix by hand; the obvious lines in setupext.py and __init__py
need to be changed to something like:

    if not ( (int(nn[0]) == 1 and int(nn[1]) >= 1) or (int(nn[0]) > 1) ):

I haven't kept up with the recent discussion about how to
number the next numpy (there was some back and forth about
how soon to move to 2.x), but sooner or later it will get
up to 2.x, so this should be fixed in the mpl repo.

Cheers,
Tom


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

Hi-

This is probably a low-probability event, however it may be
worth noting that the check for the Tk framework location in
setupext.py's detect_tkinter_darwin examines possible framework
paths in a different order than they are checked in Python's
setup.py for the purpose of building _tkinter.  Python's
setup.py searches:

/Library/Frameworks
/System/Library/Frameworks/
$HOME/Library/Frameworks

MPL's setupext.py searches:

$HOME/Library/Frameworks
/Library/Frameworks
/System/Library/Frameworks/

If a user has installed more than one new (non-Apple) Tcl/Tk,
it is possible for MPL and _tkinter to link against different
frameworks.  I think MPL does some version checking that
would prevent a build if there is a mismatch, but the source
of the difficulty may not be obvious to the installer.

The Snow Leopard Xcode man page for ld says the following about
ld's framework searching:

 The default framework search path is /Library/Frameworks then 
 /System/Library/Frameworks.

It says nothing about searching under $HOME.  So from the
point of view of Xcode it looks like there is no "right"
order between the two options, but MPL's looks "right" to me,
i.e., if a user has installed something under $HOME, the
user probably intends it to override the system.

-Tom


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/