[Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-28 Thread David Cournapeau
Hi,

I am pleased to announce the release of the rc1 for numpy
1.3.0. You can find source tarballs and installers for both Mac OS X
and Windows on the sourceforge page:

https://sourceforge.net/projects/numpy/


The release note for the 1.3.0 release are below,

The Numpy developers

=
NumPy 1.3.0 Release Notes
=

This minor includes numerous bug fixes, official python 2.6 support, and
several new features such as generalized ufuncs.

Highlights
==

Python 2.6 support
~~

Python 2.6 is now supported on all previously supported platforms, including
windows.

http://www.python.org/dev/peps/pep-0361/

Generalized ufuncs
~~

There is a general need for looping over not only functions on scalars
but also
over functions on vectors (or arrays), as explained on
http://scipy.org/scipy/numpy/wiki/GeneralLoopingFunctions. We propose to
realize this concept by generalizing the universal functions (ufuncs), and
provide a C implementation that adds ~500 lines to the numpy code base. In
current (specialized) ufuncs, the elementary function is limited to
element-by-element operations, whereas the generalized version supports
"sub-array" by "sub-array" operations. The Perl vector library PDL
provides a
similar functionality and its terms are re-used in the following.

Each generalized ufunc has information associated with it that states
what the
"core" dimensionality of the inputs is, as well as the corresponding
dimensionality of the outputs (the element-wise ufuncs have zero core
dimensions). The list of the core dimensions for all arguments is called the
"signature" of a ufunc. For example, the ufunc numpy.add has signature
"(),()->()" defining two scalar inputs and one scalar output.

Another example is (see the GeneralLoopingFunctions page) the function
inner1d(a,b) with a signature of "(i),(i)->()". This applies the inner
product
along the last axis of each input, but keeps the remaining indices
intact. For
example, where a is of shape (3,5,N) and b is of shape (5,N), this will
return
an output of shape (3,5). The underlying elementary function is called 3*5
times. In the signature, we specify one core dimension "(i)" for each
input and
zero core dimensions "()" for the output, since it takes two 1-d arrays and
returns a scalar. By using the same name "i", we specify that the two
corresponding dimensions should be of the same size (or one of them is
of size
1 and will be broadcasted).

The dimensions beyond the core dimensions are called "loop" dimensions.
In the
above example, this corresponds to (3,5).

The usual numpy "broadcasting" rules apply, where the signature
determines how
the dimensions of each input/output object are split into core and loop
dimensions:

While an input array has a smaller dimensionality than the corresponding
number
of core dimensions, 1's are pre-pended to its shape.  The core
dimensions are
removed from all inputs and the remaining dimensions are broadcasted;
defining
the loop dimensions.  The output is given by the loop dimensions plus the
output core dimensions.

Experimental Windows 64 bits support


Numpy can now be built on windows 64 bits (amd64 only, not IA64), with
both MS
compilers and mingw-w64 compilers:

This is *highly experimental*: DO NOT USE FOR PRODUCTION USE. See
INSTALL.txt,
Windows 64 bits section for more information on limitations and how to
build it
by yourself.

New features


Formatting issues
~

Float formatting is now handled by numpy instead of the C runtime: this
enables
locale independent formatting, more robust fromstring and related methods.
Special values (inf and nan) are also more consistent across platforms
(nan vs
IND/NaN, etc...), and more consistent with recent python formatting work (in
2.6 and later).

Nan handling in max/min
~~~

The maximum/minimum ufuncs now reliably propagate nans. If one of the
arguments is a nan, then nan is retured. This affects np.min/np.max,
amin/amax
and the array methods max/min. New ufuncs fmax and fmin have been added
to deal
with non-propagating nans.

Nan handling in sign


The ufunc sign now returns nan for the sign of anan.


New ufuncs
~~

#. fmax - same as maximum for integer types and non-nan floats. Returns the
   non-nan argument if one argument is nan and returns nan if both arguments
   are nan.
#. fmin - same as minimum for integer types and non-nan floats. Returns the
   non-nan argument if one argument is nan and returns nan if both arguments
   are nan.
#. deg2rad - converts degrees to radians, same as the radians ufunc.
#. rad2deg - converts radians to degrees, same as the degrees ufunc.
#. log2 - base 2 logarithm.
#. exp2 - base 2 exponential.
#. trunc - truncate floats to nearest integer towards zero.
#. logaddexp - add numbers stored as logarithms and return the

Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-28 Thread Robert Pyle
Hi all,

On Mar 28, 2009, at 9:26 AM, David Cournapeau wrote:
> I am pleased to announce the release of the rc1 for numpy
> 1.3.0. You can find source tarballs and installers for both Mac OS X
> and Windows on the sourceforge page:
>
> https://sourceforge.net/projects/numpy/
> 

I have a PPC Mac, dual G5, running 10.5.6.

The Mac OS X installer (numpy-1.3.0rc1-py2.5-macosx10.5.dmg) did not  
work for me.  It said none of my disks were suitable for  
installation.  The last time around, numpy-1.3.0b1-py2.5- 
macosx10.5.dmg persisted in installing itself into the system python  
rather than the Enthought distribution that I use, so I installed that  
version from the source tarball.

This time, installing from the source tarball also went smoothly.

Testing seems okay:
 >>> np.test()
Running unit tests for numpy
NumPy version 1.3.0rc1
NumPy is installed in /Library/Frameworks/Python.framework/Versions/ 
4.1.30101/lib/python2.5/site-packages/numpy
Python version 2.5.2 |EPD Py25 4.1.30101| (r252:60911, Dec 19 2008,  
15:28:32) [GCC 4.0.1 (Apple Computer, Inc. build 5370)]
nose version 0.10.3
 
 
 
 
 
 
 
K...K... 
 
 
 
 
 
 
 
...S..
--
Ran 2030 tests in 13.930s

OK (KNOWNFAIL=2, SKIP=1)


Bob

___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-28 Thread Robert Pyle
Hi all,
On Mar 28, 2009, at 9:26 AM, David Cournapeau wrote:
>
> I am pleased to announce the release of the rc1 for numpy
> 1.3.0. You can find source tarballs and installers for both Mac OS X
> and Windows on the sourceforge page:
>
> https://sourceforge.net/projects/numpy/
> 

On my Intel Mac (MacBook Pro), the OS X installer refused to recognize  
my disk as an installation target, just as it did on my dual G5 PPC.

Installation from the tarball was successful, and numpy.test() was  
okay (KNOWNFAIL=1, SKIP=1).

Bob

___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-28 Thread David Cournapeau
Hi Robert,

Thanks for the report.

On Sun, Mar 29, 2009 at 12:10 AM, Robert Pyle  wrote:
> Hi all,
>
> On Mar 28, 2009, at 9:26 AM, David Cournapeau wrote:
>> I am pleased to announce the release of the rc1 for numpy
>> 1.3.0. You can find source tarballs and installers for both Mac OS X
>> and Windows on the sourceforge page:
>>
>> https://sourceforge.net/projects/numpy/
>> 
>
> I have a PPC Mac, dual G5, running 10.5.6.
>
> The Mac OS X installer (numpy-1.3.0rc1-py2.5-macosx10.5.dmg) did not
> work for me.  It said none of my disks were suitable for
> installation.

Hm, strange, I have never encountered this problem. To be sure I
understand, you could open/mount the .dmg, but the .pkg refuses to
install ?

>  The last time around, numpy-1.3.0b1-py2.5-
> macosx10.5.dmg persisted in installing itself into the system python
> rather than the Enthought distribution that I use, so I installed that
> version from the source tarball.

I am afraid there is nothing I can do here - the installer can only
work with the system python I believe (or more exactly the python
version I built the package against).

Maybe people more familiar with bdist_mpkg could prove me wrong ?

cheers,

David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-28 Thread Robert Pyle
Hi David,

On Mar 28, 2009, at 12:04 PM, David Cournapeau wrote:

> Hi Robert,
>
> Thanks for the report.
>
> On Sun, Mar 29, 2009 at 12:10 AM, Robert Pyle  
>  wrote:

>> The Mac OS X installer (numpy-1.3.0rc1-py2.5-macosx10.5.dmg) did not
>> work for me.  It said none of my disks were suitable for
>> installation.
>
> Hm, strange, I have never encountered this problem. To be sure I
> understand, you could open/mount the .dmg, but the .pkg refuses to
> install ?

Yes.  When it gets to "Select a Destination", I would expect my boot  
disk to get the green arrow as the installation target, but it (and  
the other three disks) have the exclamation point in the red circle.   
Same thing happened on my MacBook Pro (Intel) with its one disk.

As I noted before, however, installation from source went without  
problems on both machines.

Bob

___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-28 Thread Alan G Isaac
On 3/28/2009 9:26 AM David Cournapeau apparently wrote:
> I am pleased to announce the release of the rc1 for numpy
> 1.3.0. You can find source tarballs and installers for both Mac OS X
> and Windows on the sourceforge page:
> https://sourceforge.net/projects/numpy/

Was the Python 2.6 Superpack intentionally omitted?

Alan Isaac


___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-29 Thread David Cournapeau
On Sun, Mar 29, 2009 at 10:09 AM, Alan G Isaac  wrote:
> On 3/28/2009 9:26 AM David Cournapeau apparently wrote:
>> I am pleased to announce the release of the rc1 for numpy
>> 1.3.0. You can find source tarballs and installers for both Mac OS X
>> and Windows on the sourceforge page:
>> https://sourceforge.net/projects/numpy/
>
> Was the Python 2.6 Superpack intentionally omitted?

No, I've added it. The 64 bits binary will come later

David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-29 Thread David Cournapeau
Robert Pyle wrote:
>
> Yes.  When it gets to "Select a Destination", I would expect my boot  
> disk to get the green arrow as the installation target, but it (and  
> the other three disks) have the exclamation point in the red circle.   
> Same thing happened on my MacBook Pro (Intel) with its one disk.
>   

Now that I think about it, maybe this is due to the lack of a python
interpreter from python.org on your side. Did you install any other
python besides the one included in EPD ? If that's the problem, we
should at least mention somewhere that the python from python.org is needed.

cheers,

David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-29 Thread Robert Pyle
Hi David,

On Mar 29, 2009, at 4:03 AM, David Cournapeau wrote:

> Robert Pyle wrote:
>>
>> Yes.  When it gets to "Select a Destination", I would expect my boot
>> disk to get the green arrow as the installation target, but it (and
>> the other three disks) have the exclamation point in the red circle.
>> Same thing happened on my MacBook Pro (Intel) with its one disk.
>>
>
> Now that I think about it, maybe this is due to the lack of a python
> interpreter from python.org on your side. Did you install any other
> python besides the one included in EPD ? If that's the problem, we
> should at least mention somewhere that the python from python.org is  
> needed.

Okay, I just installed 2.6.1 from python.org, and it is now the  
version that starts when I type "python" to Terminal.  I still cannot  
install numpy-1.3.0rc1 from the OS X installer, numpy-1.3.0rc1-py2.5- 
macosx10.5.dmg

Bob

___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-29 Thread David Cournapeau
On Sun, Mar 29, 2009 at 7:43 AM, Robert Pyle  wrote:
> Hi David,
>
> On Mar 29, 2009, at 4:03 AM, David Cournapeau wrote:
>
>> Robert Pyle wrote:
>>>
>>> Yes.  When it gets to "Select a Destination", I would expect my boot
>>> disk to get the green arrow as the installation target, but it (and
>>> the other three disks) have the exclamation point in the red circle.
>>> Same thing happened on my MacBook Pro (Intel) with its one disk.
>>>
>>
>> Now that I think about it, maybe this is due to the lack of a python
>> interpreter from python.org on your side. Did you install any other
>> python besides the one included in EPD ? If that's the problem, we
>> should at least mention somewhere that the python from python.org is
>> needed.
>
> Okay, I just installed 2.6.1 from python.org, and it is now the
> version that starts when I type "python" to Terminal.  I still cannot
> install numpy-1.3.0rc1 from the OS X installer, numpy-1.3.0rc1-py2.5-
> macosx10.5.dmg

Yes, you can't install a python 2.5 package on python 2.6. It is
almost like installing from sources is actually easier than from an
installer on mac os x...

I can relatively easily provide a 2.6 installer, though.

cheers,

David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-29 Thread Robert Pyle

On Mar 29, 2009, at 10:53 AM, David Cournapeau wrote:

> On Sun, Mar 29, 2009 at 7:43 AM, Robert Pyle  
>  wrote:
>> Hi David,
>>
>> On Mar 29, 2009, at 4:03 AM, David Cournapeau wrote:
>>
>>> Robert Pyle wrote:

 Yes.  When it gets to "Select a Destination", I would expect my  
 boot
 disk to get the green arrow as the installation target, but it (and
 the other three disks) have the exclamation point in the red  
 circle.
 Same thing happened on my MacBook Pro (Intel) with its one disk.

>>>
>>> Now that I think about it, maybe this is due to the lack of a python
>>> interpreter from python.org on your side. Did you install any other
>>> python besides the one included in EPD ? If that's the problem, we
>>> should at least mention somewhere that the python from python.org is
>>> needed.
>>
>> Okay, I just installed 2.6.1 from python.org, and it is now the
>> version that starts when I type "python" to Terminal.  I still cannot
>> install numpy-1.3.0rc1 from the OS X installer, numpy-1.3.0rc1-py2.5-
>> macosx10.5.dmg
>
> Yes, you can't install a python 2.5 package on python 2.6. It is
> almost like installing from sources is actually easier than from an
> installer on mac os x...

I just installed 2.5.4 from python.org, and the OS X installer still  
doesn't work.  This is on a PPC G5; I haven't tried it on my Intel  
MacBook Pro.

Bob
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-29 Thread David Cournapeau
On Mon, Mar 30, 2009 at 3:36 AM, Robert Pyle  wrote:

>
> I just installed 2.5.4 from python.org, and the OS X installer still
> doesn't work.  This is on a PPC G5; I haven't tried it on my Intel
> MacBook Pro.

I think I got it. To build numpy, I use virtualenv to make a
"bootstrap" environment, but then the corresponding python path get
embedded in the .mpkg - so unless you have your python interpreter in
exactly the same path as my bootstrap (which is very unlikely), it
won't run at all. This would also explain why I never saw the problem.

I will prepare a new binary,

cheers,

David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-30 Thread David Cournapeau
David Cournapeau wrote:
> On Mon, Mar 30, 2009 at 3:36 AM, Robert Pyle  wrote:
>
>   
>> I just installed 2.5.4 from python.org, and the OS X installer still
>> doesn't work.  This is on a PPC G5; I haven't tried it on my Intel
>> MacBook Pro.
>> 

Could you try this one ?

http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy/numpy-1.3.0rc1-py2.5-macosx10.5.mpkg.tbz2

If it does not work, getting the /var/tmp/install.log would be helpful
(the few last lines),

cheers,

David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-30 Thread David Cournapeau
Peter wrote:
> On Sat, Mar 28, 2009 at 2:26 PM, David Cournapeau
>  wrote:
>   
>> Hi,
>>
>> I am pleased to announce the release of the rc1 for numpy
>> 1.3.0. You can find source tarballs and installers for both Mac OS X
>> and Windows on the sourceforge page:
>>
>> https://sourceforge.net/projects/numpy/
>> 
>
> For the beta release, I can see both
> numpy-1.3.0b1-win32-superpack-python2.5.exe and
> numpy-1.3.0b1-win32-superpack-python2.6.exe
>
> However, for the first release candidate I can only see
> numpy-1.3.0rc1-win32-superpack-python2.5.exe - no Python 2.6 version.

I uploaded it but forgot to update it on the sourceforge download page.
This should be fixed,

David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-30 Thread Robert Cimrman
Hi,

It might be too late (I was off-line last week), but anyway:
I have set the milestone for the ticket 1036 [1] to 1.4, but it does not 
change the existing functionality, brings some new one, and the tests 
pass, so I wonder if it could get it into the 1.3 release?

cheers,
r.

[1] http://projects.scipy.org/numpy/ticket/1036

David Cournapeau wrote:
> Hi,
> 
> I am pleased to announce the release of the rc1 for numpy
> 1.3.0. You can find source tarballs and installers for both Mac OS X
> and Windows on the sourceforge page:
> 
> https://sourceforge.net/projects/numpy/
> 
> 
> The release note for the 1.3.0 release are below,
> 
> The Numpy developers
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-03-30 Thread Peter
On Sat, Mar 28, 2009 at 2:26 PM, David Cournapeau
 wrote:
>
> Hi,
>
> I am pleased to announce the release of the rc1 for numpy
> 1.3.0. You can find source tarballs and installers for both Mac OS X
> and Windows on the sourceforge page:
>
> https://sourceforge.net/projects/numpy/

For the beta release, I can see both
numpy-1.3.0b1-win32-superpack-python2.5.exe and
numpy-1.3.0b1-win32-superpack-python2.6.exe

However, for the first release candidate I can only see
numpy-1.3.0rc1-win32-superpack-python2.5.exe - no Python 2.6 version.
Is this an oversight, or maybe some caching issue with the sourceforge
mirror system?  In the meantime I'll give the beta a go on Python 2.6
on my Windows XP machine...

Thanks,

Peter
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] [Announce] Numpy 1.3.0 rc1

2009-04-01 Thread Tommy Grav

On Mar 30, 2009, at 2:56 AM, David Cournapeau wrote:

> On Mon, Mar 30, 2009 at 3:36 AM, Robert Pyle  
>  wrote:
>
>>
>> I just installed 2.5.4 from python.org, and the OS X installer still
>> doesn't work.  This is on a PPC G5; I haven't tried it on my Intel
>> MacBook Pro.
>
> I think I got it. To build numpy, I use virtualenv to make a
> "bootstrap" environment, but then the corresponding python path get
> embedded in the .mpkg - so unless you have your python interpreter in
> exactly the same path as my bootstrap (which is very unlikely), it
> won't run at all. This would also explain why I never saw the problem.
>
This is exactly the problem. This is the error message that you get
when running the .dmg and no hard drives are available for selection.

You cannot install numpy 1.3.0rc1 on this volume.
  numpy requires /Users/david/src/dsp/numpy/1.3.x/bootstrap Python 2.5  
to install.


> I will prepare a new binary,

Any idea when a new binary will be available on sourceforge.net?

Cheers
Tommy
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion