Re: [Numpy-discussion] Toward a numpy build with warning: handling unused variable

2008-08-04 Thread Dag Sverre Seljebotn
David Cournapeau wrote: On Mon, 2008-08-04 at 01:50 +0200, Stéfan van der Walt wrote: Just to be clear: I meant that I agree with you that we should see NumPy related warnings that aren't smothered in bogus messages. Is there no way to do this without compiler-specific hacks? Yes, there

Re: [Numpy-discussion] arrays : c aligmen to fortran and back

2008-08-04 Thread Stéfan van der Walt
Hi Thomas 2008/8/4 Thomas Hrabe [EMAIL PROTECTED]: I need to convert a 3d array from c alingment to fortran and was wandering for the simplest code available. Its all about python and an interfaced C++ program, which, however, processes fortran aligned arrays. Is there a simple code from

Re: [Numpy-discussion] numpy 1.1.rc2: win32 binaries

2008-08-04 Thread Bruce Southey
Hi, I installed the 'official binaries' on a Intel Celeron M 530 that supports SSE2 and SSE3 running MS Vista. All tests passed and with regards to the ticket: numpy.inner(F,F) resulted in 'array([[ Inf]])' Regards Bruce On Sat, Aug 2, 2008 at 7:36 PM, Jarrod Millman [EMAIL PROTECTED] wrote:

Re: [Numpy-discussion] numpy 1.1.rc2: win32 binaries

2008-08-04 Thread David Cournapeau
Bruce Southey wrote: Hi, I installed the 'official binaries' on a Intel Celeron M 530 that supports SSE2 and SSE3 running MS Vista. All tests passed and with regards to the ticket: numpy.inner(F,F) resulted in 'array([[ Inf]])' I thought that problem had be gone for good, but you're

Re: [Numpy-discussion] numpy 1.1.rc2: win32 binaries

2008-08-04 Thread David Cournapeau
Bruce Southey wrote: Hi, I installed the 'official binaries' on a Intel Celeron M 530 that supports SSE2 and SSE3 running MS Vista. All tests passed and with regards to the ticket: numpy.inner(F,F) resulted in 'array([[ Inf]])' Ok, it looks like this is entirely due to my own stupidity.

[Numpy-discussion] concatenate an array with a number

2008-08-04 Thread Nicolas Chopin
Hi list, I want to do this: y = concatenate(x[0],x) where x is a 1d array. However, the only way I managed to make this work is: y = concatenate( array((x[0],),ndmin=1), x) which is kind of cryptic. (If I remove ndmin, numpy still complains.) 1. Is there a better way? 2. Would it be

Re: [Numpy-discussion] concatenate an array with a number

2008-08-04 Thread Robert Kern
On Mon, Aug 4, 2008 at 09:58, Nicolas Chopin [EMAIL PROTECTED] wrote: Hi list, I want to do this: y = concatenate(x[0],x) where x is a 1d array. However, the only way I managed to make this work is: y = concatenate( array((x[0],),ndmin=1), x) which is kind of cryptic. (If I remove

Re: [Numpy-discussion] concatenate an array with a number

2008-08-04 Thread Robin
On Mon, Aug 4, 2008 at 3:58 PM, Nicolas Chopin [EMAIL PROTECTED] wrote: Hi list, I want to do this: y = concatenate(x[0],x) where x is a 1d array. However, the only way I managed to make this work is: y = concatenate( array((x[0],),ndmin=1), x) which is kind of cryptic. (If I remove

Re: [Numpy-discussion] concatenate an array with a number

2008-08-04 Thread Pierre GM
On Monday 04 August 2008 10:58:00 Nicolas Chopin wrote: Hi list, I want to do this: y = concatenate(x[0],x) where x is a 1d array. However, the only way I managed to make this work is: y = concatenate( array((x[0],),ndmin=1), x) which is kind of cryptic. (If I remove ndmin, numpy still

[Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Pierre GM
All, * What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0 (w/o support to Python 2.3) ? I need to correct an elusive bug in numpy.ma.MaskedArray and wondered whether I needed to backport it or not (1.1.x would likely be affected as well). Thanks a lot in advance, P.

Re: [Numpy-discussion] Toward a numpy build with warning: handling unused variable

2008-08-04 Thread Lisandro Dalcin
David, I second your approach. Furthermore, look how SWIG handles this, it is very similar to your proposal. The difference is that SWIG uses SWIGUNUSED for some autogenerated functions. Furthermore, it seems the SWIG developers protected the generated code taking into account GCC versions ;-) and

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Jarrod Millman
On Mon, Aug 4, 2008 at 9:49 AM, Pierre GM [EMAIL PROTECTED] wrote: * What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0 (w/o support to Python 2.3) ? There are currently no plans for 1.1.2. Not that it won't happen; it's just that there hasn't been any plans for the

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Charles R Harris
HI Pierre, On Mon, Aug 4, 2008 at 11:49 AM, Pierre GM [EMAIL PROTECTED] wrote: All, * What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0 (w/o support to Python 2.3) ? I need to correct an elusive bug in numpy.ma.MaskedArray and wondered whether I needed to backport it

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Jarrod Millman
On Mon, Aug 4, 2008 at 10:10 AM, Jarrod Millman [EMAIL PROTECTED] wrote: Here is the current 1.2.0 schedule: - 8/08/08 tag the 1.2.0rc1 release and prepare packages - 8/15/08 tag the 1.2.0rc2 release and prepare packages - 8/23/08 tag the 1.2.0 release and prepare packages -

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Jarrod Millman
On Mon, Aug 4, 2008 at 10:17 AM, Charles R Harris [EMAIL PROTECTED] wrote: I don't know what the schedule is, but if you have a bug fix it is probably a good idea to back port it to 1.1.x so that any future release will be easier. Also, if you do do the backport, put an informative comment

[Numpy-discussion] 1.2 tasks

2008-08-04 Thread Jarrod Millman
Here are the remaining tasks that I am aware of that need to be done before tagging 1.2.0b1 on the 8th. Median == The call signature for median needs to change from def median(a, axis=0, out=None, overwrite_input=False): to def median(a, axis=None, out=None, overwrite_input=False): in

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Pierre GM
Charles, Jarrod, That isn't be a pb. I just ran into a pb with 1.2 that I know would show up in 1.1.x, so I just commited the changes to the 2 versions. I was just wondering for how long I would have to backport this kind of fixes. I agree with the caveat that your focus should be mostly on

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Darren Dale
Hi Jarrod, I was wondering if someone knowledgeable would please look into the behavior of concatenate() with subclasses of ndarray. I posted at scipy-dev some work on a subclass that handles units, and when two of these are concatenated, a regular ndarray is returned rather than another

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Charles R Harris
On Mon, Aug 4, 2008 at 12:31 PM, Jarrod Millman [EMAIL PROTECTED]wrote: On Mon, Aug 4, 2008 at 10:17 AM, Charles R Harris [EMAIL PROTECTED] wrote: I don't know what the schedule is, but if you have a bug fix it is probably a good idea to back port it to 1.1.x so that any future release

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Charles R Harris
On Mon, Aug 4, 2008 at 1:07 PM, Pierre GM [EMAIL PROTECTED] wrote: Charles, Jarrod, That isn't be a pb. I just ran into a pb with 1.2 that I know would show up in 1.1.x, so I just commited the changes to the 2 versions. I was just wondering for how long I would have to backport this kind of

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread David Huard
On Mon, Aug 4, 2008 at 1:45 PM, Jarrod Millman [EMAIL PROTECTED] wrote: Here are the remaining tasks that I am aware of that need to be done before tagging 1.2.0b1 on the 8th. Median == The call signature for median needs to change from def median(a, axis=0, out=None,

Re: [Numpy-discussion] What/when is the next release ?

2008-08-04 Thread Robert Kern
On Mon, Aug 4, 2008 at 13:40, Charles R Harris [EMAIL PROTECTED] wrote: On Mon, Aug 4, 2008 at 1:07 PM, Pierre GM [EMAIL PROTECTED] wrote: Charles, Jarrod, That isn't be a pb. I just ran into a pb with 1.2 that I know would show up in 1.1.x, so I just commited the changes to the 2 versions.

Re: [Numpy-discussion] import numpy is slow

2008-08-04 Thread Christopher Barker
Robert Kern wrote: It isn't. The problem is on Chris's file system. Thanks for all your help, Robert. Interestingly, I haven't noticed any problems anywhere else, but who knows? I guess this is what Linux Torvalds meant when he said that OS-X's file system was brain dead Whatever is wrong

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Pierre GM
On Monday 04 August 2008 13:45:51 Jarrod Millman wrote: Here are the remaining tasks that I am aware of that need to be done before tagging 1.2.0b1 on the 8th. The call signature for median needs to change from def median(a, axis=0, out=None, overwrite_input=False): to def median(a,

Re: [Numpy-discussion] import numpy is slow

2008-08-04 Thread Robert Kern
On Mon, Aug 4, 2008 at 14:24, Christopher Barker [EMAIL PROTECTED] wrote: Robert Kern wrote: It isn't. The problem is on Chris's file system. Thanks for all your help, Robert. Interestingly, I haven't noticed any problems anywhere else, but who knows? I guess this is what Linux Torvalds

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Pierre GM
On Monday 04 August 2008 14:16:33 Darren Dale wrote: Hi Jarrod, I was wondering if someone knowledgeable would please look into the behavior of concatenate() with subclasses of ndarray. Darren, I ran into similar problems when I started working on numpy.ma and scikits.timeseries, and I

[Numpy-discussion] WTFM!

2008-08-04 Thread Joe Harrington
SciPy Documentation Marathon 2008 Status Report We are now nearing the end of the summer. We have a ton of great docstrings, a nice PDF and HTML reference guide, a new package with pages on general topics like slicing, and a glossary. We had hoped to have all the numpy docstrings in

Re: [Numpy-discussion] arrays : c aligmen to fortran and back

2008-08-04 Thread Thomas Hrabe
Yeah, this function does the job. Thank you very much! -Original Message- From: [EMAIL PROTECTED] on behalf of Stéfan van der Walt Sent: Mon 8/4/2008 1:41 AM To: Discussion of Numerical Python Subject: Re: [Numpy-discussion] arrays : c aligmen to fortran and back Hi Thomas 2008/8/4

Re: [Numpy-discussion] arrays : c aligmen to fortran and back

2008-08-04 Thread Thomas Hrabe
PS: is there any public C library available which would perform the same operation? like void* swap(int numberDimensions,int sizeDimensions,int dataSize,int conversionType,void* data); where conversionType is the flag fortran to c or vice versa. As it works for numpy, there should be some

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Darren Dale
Hi Pierre, On Monday 04 August 2008 04:29:57 pm Pierre GM wrote: On Monday 04 August 2008 14:16:33 Darren Dale wrote: Hi Jarrod, I was wondering if someone knowledgeable would please look into the behavior of concatenate() with subclasses of ndarray. Darren, I ran into similar

[Numpy-discussion] boolean defaults for svd

2008-08-04 Thread Keith Goodman
svd uses 1 for its defaults: svd(a, full_matrices=1, compute_uv=1) Anyone interested in changing 1 to True? It shouldn't break any code, right? ___ Numpy-discussion mailing list Numpy-discussion@scipy.org

Re: [Numpy-discussion] 1.2 tasks

2008-08-04 Thread Darren Dale
On Monday 04 August 2008 6:27:12 pm you wrote: On Monday 04 August 2008 17:53:54 you wrote: In my example, it is not just that concat is stripping the units, it is returning a different type. By that, you mean that the result is not a NDQuantity ? Ah. As you mentioned Travis' email,

Re: [Numpy-discussion] import numpy is slow

2008-08-04 Thread Christopher Barker
OK, So I'm an idiot. After reading this, I thought I haven't rebooted for a while. It turns out it's been 35 days. I think I've been having slow startup for a longer than that, but none the less, I re-booted (which took a long time), and presto: $ time python -c import numpy real0m0.686s

Re: [Numpy-discussion] import numpy is slow

2008-08-04 Thread Robert Kern
On Mon, Aug 4, 2008 at 18:01, Christopher Barker [EMAIL PROTECTED] wrote: OK, So I'm an idiot. After reading this, I thought I haven't rebooted for a while. It turns out it's been 35 days. I think I've been having slow startup for a longer than that, but none the less, I re-booted (which

[Numpy-discussion] running numpy tests

2008-08-04 Thread Andrew Dalke
I'm working on the patches for reducing the import overhead. I want to make sure I don't break anything. I'm trying to figure out how to run all of the tests. I expected, based on the following Alan McIntyre wrote: They actually do two different things; numpy.test() runs test for all of

Re: [Numpy-discussion] running numpy tests

2008-08-04 Thread Robert Kern
On Mon, Aug 4, 2008 at 18:15, Andrew Dalke [EMAIL PROTECTED] wrote: I'm working on the patches for reducing the import overhead. I want to make sure I don't break anything. I'm trying to figure out how to run all of the tests. I expected, based on the following Alan McIntyre wrote: They

Re: [Numpy-discussion] running numpy tests

2008-08-04 Thread Andrew Dalke
On Aug 5, 2008, at 2:00 AM, Robert Kern wrote: You have old stuff in your checkout/installation. Make sure you have deleted all of the *.pycs and directories which have been deleted in SVN. I removed all .pyc files, wiped my installation directory, and it works now as I expect it to work.

Re: [Numpy-discussion] running numpy tests

2008-08-04 Thread Andrew Dalke
On Aug 5, 2008, at 2:00 AM, Robert Kern wrote: You have old stuff in your checkout/installation. Make sure you have deleted all of the *.pycs and directories which have been deleted in SVN. Now that I've fixed that, I can tell that I made a mistake related to the self-test code. I can't

Re: [Numpy-discussion] running numpy tests

2008-08-04 Thread Robert Kern
On Mon, Aug 4, 2008 at 20:41, Andrew Dalke [EMAIL PROTECTED] wrote: On Aug 5, 2008, at 2:00 AM, Robert Kern wrote: You have old stuff in your checkout/installation. Make sure you have deleted all of the *.pycs and directories which have been deleted in SVN. Now that I've fixed that, I can