[Numpy-discussion] status of numpy 1.3.0

Francesc Alted faltet@pytables....
Mon Nov 24 12:34:24 CST 2008

A Monday 24 November 2008, Jarrod Millman escrigué:
> Now that scipy 0.7.0b1 has been tagged, I wanted to start planning
> for the NumPy 1.3.0:
> http://projects.scipy.org/scipy/numpy/milestone/1.3.0
> The original plan was to release 1.3 at the end of November.  At this
> point, we are going to have to push back the release date a bit.  I
> would like to get 1.3 out ASAP, so I would like aim for the third
> week of December.
> This is how I see the current development trunk:
>   * 2.6 compatablity (Linux 32- and 64-bit done, Windows 32-bit done,
> Mac 32-bit done)
>   * Generalized Ufuncs (committed)
>   * Ufunc clean-up (committed)
>   * Refactoring numpy.core math configuration (?? bump to 1.4 ??)
>   * Improvements to build warnings (?? bump to 1.4 ??)
>   * Histogram (committed)
>   * NumPy testing improvements
> (http://projects.scipy.org/scipy/numpy/ticket/957)
>   * Documentation improvements
>   * MaskedArray improvements
>   * Bugfixes
> Am I missing anything?  Is there anything else that we should get in
> before releasing 1.3?  Does it seem reasonable that we could release
> 1.3 during the third week of December?  Who will have time to work on
> NumPy for the next month?

Just went ahead and compiled the NumPy trunk version in a Windows 
platform, and although most of the nose tests of NumPy passes well 
(there are some failures, but seem harmless), my tests say there is an 
inconsistency in the positive limit value (+1.) of arctanh between 
1.2.x and 1.3.x in trunk:

Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)] on 
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> numpy.__version__
>>> numpy.arctanh(1.)
>>> numpy.isinf
<ufunc 'isinf'>
>>> numpy.isinf(numpy.arctanh(1.))
>>> numpy.arctanh(-1.)
>>> numpy.isinf(numpy.arctanh(-1.))

Python 2.6 (r26:66721, Oct  2 2008, 11:35:03) [MSC v.1500 32 bit 
(Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> numpy.__version__
>>> numpy.arctanh(1.)
>>> numpy.isinf(numpy.arctanh(1.))
>>> numpy.arctanh(-1.)
>>> numpy.isinf(numpy.arctanh(-1.))

As you see, the trunk version returns ``nan`` for arctanh(1.), while 
1.2.1 returns ``inf`` (the correct value).  For arctanh(-1.) both 
versions correctly returns ``-inf``.  I used the official binaries for 
1.2.1, while I've used the MSVC 2008 (32-bit) for compiling trunk (the 
resuilting binaries works badly in both Windows XP 32-bit and Windows 
Vista 64-bit).

My experiments on Linux shows that they both return ``+inf`` and 
``-inf``, so it seems that this is a Windows specific issue.  Should I 
file a ticket for this?


Francesc Alted

More information about the Numpy-discussion mailing list