Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-23 Thread Sebastian Haase
(please copy to the trace page) On Sat, Mar 22, 2008 at 6:08 PM, James Philbin [EMAIL PROTECTED] wrote: I'm not sure that #669 (http://projects.scipy.org/scipy/numpy/ticket/669) is a bug, but probably needs some discussion (see the last reply on that page). The cast is made because we don't

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-23 Thread James Philbin
Well that's fine for binops with the same types, but it's not so obvious which type to cast to when mixing signed and unsigned types. Should the type of N.int32(10)+N.uint32(10) be int32, uint32 or int64? Given your answer what should the type of N.int64(10)+N.uint64(10) be (which is the case in

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-21 Thread Sebastian Haase
I think the bug was referring to the fact that some types have duplicate names *explicitly* containing the letter c -- as in repr(N.intc) 'type 'numpy.int32'' Is this supposed to be consistent naming scheme (i.e. any C type T is accessible as N.Tc) ? Then c float-type should consequently be

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-21 Thread Joris De Ridder
On 21 Mar 2008, at 12:29, Sebastian Haase wrote: ... and what does the p stand for in N.intp type 'numpy.int32' It stands for pointer. An intp is an integer large enough to contain a pointer address. J. Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-19 Thread Matthieu Brucher
For the not blocker bugs, I think that #420 should be closed : float32 is the the C float type, isn't it ? Matthieu 2008/3/13, Jarrod Millman [EMAIL PROTECTED]: Hello, I am sure that everyone has noticed that 1.0.5 hasn't been released yet. The main issue is that when I was getting ready

[Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-15 Thread Stéfan van der Walt
Hi David On Fri, Mar 14, 2008 at 9:19 AM, David Huard [EMAIL PROTECTED] wrote: I added a test for ticket 691. Problem is, there seems to be a new bug. I don't know it its related to the change or if it was there before. Please check this out. Fantastic, thanks for jumping in and addressing

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-14 Thread David Huard
I added a test for ticket 690. 2008/3/13, Barry Wark [EMAIL PROTECTED]: I appologize that the Mac OSX buildbot has been so flakey. For some reason it stops being able to resolve scipy.org on a regular basis (though other processes on the same machine don't seem to have trouble). Restarting

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-14 Thread David Huard
I added a test for ticket 691. Problem is, there seems to be a new bug. I don't know it its related to the change or if it was there before. Please check this out. David 2008/3/14, David Huard [EMAIL PROTECTED]: I added a test for ticket 690. 2008/3/13, Barry Wark [EMAIL PROTECTED]: I

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-13 Thread Jarrod Millman
On Wed, Mar 12, 2008 at 10:43 PM, Jarrod Millman [EMAIL PROTECTED] wrote: Stefan and I also triaged the remaining tickets--closing several and turning others in to release blockers: http://scipy.org/scipy/numpy/query?status=newseverity=blockermilestone=1.0.5order=priority I think that

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

2008-03-13 Thread Barry Wark
I appologize that the Mac OSX buildbot has been so flakey. For some reason it stops being able to resolve scipy.org on a regular basis (though other processes on the same machine don't seem to have trouble). Restarting the slave fixes the issue. Anyways, if anyone is testing an OS X issue and the