[Numpy-discussion] uniform() regression(?) in svn

Hi- On PPC Mac OSX universal build 2.4.3, gcc 4.0, In [1]: import numpy as N In [2]: print N.__version__ 1.0.2897 In [3]: N.random.uniform(0,1) Segmentation fault (This originally showed up in the Ticket 83 regression test during numpy.test()...) Andrew

[Numpy-discussion] Bug in memmap/python allocation code?

My apologies if this is a duplicate - my first attempt doesn't seem to have gone back to the list.-- Forwarded message --From: Mike Ressler [EMAIL PROTECTED]Date: Jul 25, 2006 12:17 PMSubject: Re: ***[Possible UCE]*** [Numpy-discussion] Bug in memmap/python allocation code?To:

Re: [Numpy-discussion] uniform() regression(?) in svn

Andrew Jaffe wrote: Hi- On PPC Mac OSX universal build 2.4.3, gcc 4.0, In [1]: import numpy as N In [2]: print N.__version__ 1.0.2897 In [3]: N.random.uniform(0,1) Segmentation fault (This originally showed up in the Ticket 83 regression test during numpy.test()...) This

Re: [Numpy-discussion] I've created a 1.0b1 release tag in SVN

Travis Oliphant wrote: I've created the 1.0b1 release tag in SVN and will be uploading files shortly to Sourceforge. I've also created a 1.0 release branch called ver1.0 The trunk is now version 1.1 of NumPy and should be used for new-development only. I don't expect 1.1 to come out

[Numpy-discussion] Version numbers

I like the plan of adopting even-numbers for stable releases. So, if you have an odd-number then it is from the development trunk. Thus, after 1.1.SVN_number builds will come a stable 1.2 build Now, this doesn't solve the problem of what to do on the ver1.0 branch. I propose to do what