Stéfan van der Walt wrote:
> Hi John
>
> 2009/5/20 :
>
>> On Wed, May 20, 2009 at 3:07 PM, John Hunter wrote:
>>
>>> We are trying to build and test mpl installers for python2.4, 2.5 and
>>> 2.6. What we are finding is that if we build mpl against a more
>>> recent numpy than the install
2009/5/20 Stéfan van der Walt :
> David Cournapeau also put a check in place so that the NumPy build
> will break if we forget to update the API version again.
>
> So, while we can't change the releases of NumPy out there already, we
> can at least ensure that this won't happen again.
OK, great -
Hi John
2009/5/20 :
> On Wed, May 20, 2009 at 3:07 PM, John Hunter wrote:
>> We are trying to build and test mpl installers for python2.4, 2.5 and
>> 2.6. What we are finding is that if we build mpl against a more
>> recent numpy than the installed numpy on a test machine, the import of
>> mpl
On Wed, May 20, 2009 at 3:07 PM, John Hunter wrote:
> We are trying to build and test mpl installers for python2.4, 2.5 and
> 2.6. What we are finding is that if we build mpl against a more
> recent numpy than the installed numpy on a test machine, the import of
> mpl extension modules which depe
We are trying to build and test mpl installers for python2.4, 2.5 and
2.6. What we are finding is that if we build mpl against a more
recent numpy than the installed numpy on a test machine, the import of
mpl extension modules which depend on numpy trigger a segfault.
Eg, on python2.5 and python2
