[Numpy-discussion] [ANN] numpy 1.4.0 rc2

Gökhan Sever gokhansever at gmail.com
Mon Dec 28 13:15:11 EST 2009


On Mon, Dec 28, 2009 at 11:16 AM, Gökhan Sever <gokhansever at gmail.com>wrote:

>
>
> On Mon, Dec 28, 2009 at 11:07 AM, Robert Kern <robert.kern at gmail.com>wrote:
>
>> On Mon, Dec 28, 2009 at 11:00, Gökhan Sever <gokhansever at gmail.com>
>> wrote:
>>
>> > One interesting thing I have noticed while installing the numpy from the
>> > source is that numpy dependent libraries must be re-installed and this
>> must
>> > be a clean re-install. For instance I can't import some matplotlib and
>> scipy
>> > modules without making a fresh installation for these packages. My
>> attempts
>> > result with a runtime error.
>>
>> Please, please, always copy-and-paste the traceback when reporting an
>> error. I know you aren't formally reporting a bug here, but it always
>> helps.
>>
>> > Could someone clarify this point? Is this due
>> > to API change in the numpy core?
>>
>> Cython/Pyrex code does a runtime check on the struct sizes of types.
>> We have carefully added a member to the PyArrayDescr struct; i.e. it
>> shouldn't cause any actual problems, but Cython does the check
>> anyways. This affects a few modules in scipy, but shouldn't have
>> affected anything in matplotlib. The traceback may help us identify
>> the issue you are seeing.
>>
>>
> It is too late for the tracebacks. I have already removed the problematic
> packages and did clean installs. However, next time I will be more careful
> while reporting such issues. If it helps, in both matplotlib (via ipython
> -pylab) and scipy.stats import cases the runtime errors was raised due to
> numpy.core.multiarray module import.
>
>
>
>> --
>>
>> Robert Kern
>>
>> "I have come to believe that the whole world is an enigma, a harmless
>> enigma that is made terrible by our own mad attempt to interpret it as
>> though it had an underlying truth."
>>  -- Umberto Eco
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>
>
>
> --
> Gökhan
>

Here is another interesting point to consider. To reproduce the runtime
error I mentioned previously I downgraded numpy (from the latest check-out
installation) following these steps:

svn co http://svn.scipy.org/svn/numpy/branches/1.3.x/ numpy
cd numpy
python setup.py install
Writing /usr/lib/python2.6/site-packages/numpy-1.3.1.dev8031-py2.6.egg-info

I[2]: import matplotlib.pyplot as plt
Segmentation fault

I[3]: from scipy import stats
Segmentation fault

I have installed matplotlib and scipy using the latest numpy dev version. A
little later I will downgrade matplotlib and scipy to their previous stable
versions, and compile them using numpy 1.3.x. Afterwards I will update numpy
and test to see if I can re-produce the runtime error to provide the
tracebacks. First let me know if any tracebacks needed for these segfaults
or are these known failures?

================================================================================
Platform     :
Linux-2.6.29.6-217.2.3.fc11.i686.PAE-i686-with-fedora-11-Leonidas
Python       : ('CPython', 'tags/r26', '66714')
================================================================================


-- 
Gökhan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20091228/7a9461ba/attachment.html>


More information about the NumPy-Discussion mailing list