Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Andrew Dalke
On Jul 31, 2008, at 3:53 AM, David Cournapeau wrote: You are supposed to run the tests on an installed numpy, not in the sources: import numpy numpy.test(verbose = 10) Doesn't that make things more cumbersome to test? That is, if I were to make a change I would need to: - python

Re: [Numpy-discussion] Example of numpy cov() not correct?

2008-07-31 Thread Pauli Virtanen
Wed, 30 Jul 2008 18:49:10 +0300, Nadav Horesh wrote: If you read the cov function documentation you'll see that if a second vector is given, it joins the 2 into one matrix and calculate the covariance of it. In your case, you are looking for the off-diagonal elements. So the final answer to

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Hanni Ali
Hi All, I've been reading this discussion with interest. I would just to highlight an alternate use of numpy to interactive use. We have a cluster of machines which process tasks on an individual basis where a master tasks may spawn 600 slave tasks to be processed. These tasks are spread across

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Nathan Bell
On Thu, Jul 31, 2008 at 7:31 AM, Hanni Ali [EMAIL PROTECTED] wrote: I would just to highlight an alternate use of numpy to interactive use. We have a cluster of machines which process tasks on an individual basis where a master tasks may spawn 600 slave tasks to be processed. These tasks are

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread David Cournapeau
Nathan Bell wrote: There are other components of NumPy/SciPy that are more worthy of optimization. Given that programmer time is a scarce resource, it's more sensible to direct our efforts towards making the other 98.5% of the computation faster. To be fair, when I took a look at the

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Nathan Bell
On Thu, Jul 31, 2008 at 5:36 AM, Andrew Dalke [EMAIL PROTECTED] wrote: The user base for numpy might be .. 10,000 people? 100,000 people? Let's go with the latter, and assume that with command-line scripts, CGI scripts, and the other programs that people write in order to help do research

Re: [Numpy-discussion] The date/time dtype and the casting issue

2008-07-31 Thread Alan G Isaac
A Thursday 31 July 2008, Matt Knox escrigué: While on the topic of FAME... being a financial analyst, I really am quite fond of the multitude of quarterly frequencies we have in the timeseries package (with different year end points) because they are very useful when doing things like

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Gael Varoquaux
On Thu, Jul 31, 2008 at 03:41:15PM +0900, David Cournapeau wrote: Yes. Nothing that an easy make file cannot solve, nonetheless (I am sure I am not the only one with a makefile/script which automates the above, to test a new svn updated numpy in one command). That's why distutils have a test

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Gael Varoquaux
On Thu, Jul 31, 2008 at 12:43:17PM +0200, Andrew Dalke wrote: Startup performance has not been a numpy concern. It a concern for me, and it has been (for other packages) a concern for some of my clients. I am curious, if startup performance is a problem, I guess it is because you are

Re: [Numpy-discussion] Example of numpy cov() not correct?

2008-07-31 Thread Keith Goodman
On Thu, Jul 31, 2008 at 1:14 AM, Pauli Virtanen [EMAIL PROTECTED] wrote: Yes, the example on http://www.scipy.org/Numpy_Example_List_With_Doc#cov is wrong; cov(T,P) indeed returns a matrix. And it would be nice if someone fixed this, you can simply register a wiki account and fix the

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Alan McIntyre
On Thu, Jul 31, 2008 at 2:12 AM, Andrew Dalke [EMAIL PROTECTED] wrote: Hmm. And it looks like testing/nosetester.py (which implements the 'test' function above) is meant to make it easier to run nose, except my feeling is the extra level of wrapping makes things more complicated. The nosetest

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread David Cournapeau
Gael Varoquaux wrote: That's why distutils have a test target. You can do python setup.py test, and if you have setup you setup.py properly it should work (obviously it is easy to make this statement, and harder to get the thing working). I have already seen some discussion about

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Gael Varoquaux
On Thu, Jul 31, 2008 at 11:05:33PM +0900, David Cournapeau wrote: Gael Varoquaux wrote: That's why distutils have a test target. You can do python setup.py test, and if you have setup you setup.py properly it should work (obviously it is easy to make this statement, and harder to get the

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread David Cournapeau
Gael Varoquaux wrote: Obviously, the build part has to be well-tuned for the machinery to work, but there is a lot of value here. Ah yes, setuptools does have this. But this is specific to setuptools, bare distutils does not have this test command, right ? cheers, David

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Kevin Jacobs [EMAIL PROTECTED]
On Thu, Jul 31, 2008 at 10:14 AM, Gael Varoquaux [EMAIL PROTECTED] wrote: On Thu, Jul 31, 2008 at 12:43:17PM +0200, Andrew Dalke wrote: Startup performance has not been a numpy concern. It a concern for me, and it has been (for other packages) a concern for some of my clients. I am

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Gael Varoquaux
On Thu, Jul 31, 2008 at 11:16:12PM +0900, David Cournapeau wrote: Gael Varoquaux wrote: Obviously, the build part has to be well-tuned for the machinery to work, but there is a lot of value here. Ah yes, setuptools does have this. But this is specific to setuptools, bare distutils does

[Numpy-discussion] distutils and inplace build: is numpy supposed to work ?

2008-07-31 Thread David Cournapeau
Hi, I wanted to know if numpy was supposed to work when built in place through the -i option of distutils. The reason why I am asking it that I would like to support it in numscons, and I cannot make it work when using distutils. Importing numpy works in the source tree, but most tests fail

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Gael Varoquaux
On Thu, Jul 31, 2008 at 10:34:04AM -0400, Kevin Jacobs [EMAIL PROTECTED] wrote: The morale of this discussion, for me, is that just because _you_ don't care about a particular aspect or feature, doesn't mean that others don't or shouldn't. Your workarounds may not be viable for me

Re: [Numpy-discussion] [ANNOUNCE] Traits 3.0 has been released

2008-07-31 Thread Kevin Jacobs [EMAIL PROTECTED]
On Wed, Jul 30, 2008 at 9:25 PM, Dave Peterson [EMAIL PROTECTED]wrote: Hello, I am very pleased to announce that Traits 3.0 has just been released! All of the URLs on PyPi to Enthought seem to be broken (e.g., http://code.enthought.com/traits). Can you give an example showing how traits

Re: [Numpy-discussion] [ANNOUNCE] Traits 3.0 has been released

2008-07-31 Thread Gael Varoquaux
On Thu, Jul 31, 2008 at 10:38:42AM -0400, Kevin Jacobs [EMAIL PROTECTED] wrote: All of the URLs on PyPi to Enthought seem to be broken (e.g., [2]http://code.enthought.com/traits). Can you give an example showing how traits work? I'm mildly intrigued, but too lazy to dig beyond the

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Christopher Barker
Andrew Dalke wrote: If I had my way, remove things like (in numpy/__init__.py) import linalg import fft import random import ctypeslib import ma as a side benefit, this might help folks using py2exe, py2app and friends -- as it stands all those sub-modules need

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread David Cournapeau
Christopher Barker wrote: On my OS-X box (10.4.11, python2.5, numpy '1.1.1rc2'), it takes about 7 seconds to import numpy! Hot or cold ? If hot, there is something horribly wrong with your setup. On my macbook, it takes ~ 180 ms to to python -c import numpy, and ~ 100 ms on linux (same

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Christopher Barker
Stéfan van der Walt wrote: No one is *waiting* for NumPy to start. I am, and probably 10 times, a day, yes. And it's a major issue for CGI, though maybe no one's using that anymore anyway. Just by answering this e-mail I could have (and maybe should have) started NumPy three hundred and

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Christopher Barker
David Cournapeau wrote: Christopher Barker wrote: On my OS-X box (10.4.11, python2.5, numpy '1.1.1rc2'), it takes about 7 seconds to import numpy! Hot or cold ? If hot, there is something horribly wrong with your setup. hot -- it takes about 10 cold. I've been wondering about that. time

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Nils Wagner
On Thu, 31 Jul 2008 10:12:22 -0700 Christopher Barker [EMAIL PROTECTED] wrote: David Cournapeau wrote: Christopher Barker wrote: On my OS-X box (10.4.11, python2.5, numpy '1.1.1rc2'), it takes about 7 seconds to import numpy! Hot or cold ? If hot, there is something horribly wrong with

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread David Huard
On Thu, Jul 31, 2008 at 1:12 PM, Christopher Barker [EMAIL PROTECTED]wrote: David Cournapeau wrote: Christopher Barker wrote: On my OS-X box (10.4.11, python2.5, numpy '1.1.1rc2'), it takes about 7 seconds to import numpy! Hot or cold ? If hot, there is something horribly wrong with

[Numpy-discussion] Numpy 1.1.1 release notes.

2008-07-31 Thread Charles R Harris
Hi All, I've attached draft release notes for Numpy 1.1.1. If you have anything to add or correct, let me know. Chuck Numpy 1.1.1 is a bug fix release featuring major improvements in Python 2.3.x compatibility and masked arrays. Python 2.3.x fixes Robert Kern -- remove developement

Re: [Numpy-discussion] The date/time dtype and the casting issue

2008-07-31 Thread Francesc Alted
A Thursday 31 July 2008, Alan G Isaac escrigué: A Thursday 31 July 2008, Matt Knox escrigué: While on the topic of FAME... being a financial analyst, I really am quite fond of the multitude of quarterly frequencies we have in the timeseries package (with different year end points) because

Re: [Numpy-discussion] distutils and inplace build: is numpy supposed to work ?

2008-07-31 Thread Charles R Harris
On Thu, Jul 31, 2008 at 8:18 AM, David Cournapeau [EMAIL PROTECTED] wrote: Hi, I wanted to know if numpy was supposed to work when built in place through the -i option of distutils. The reason why I am asking it that I would like to support it in numscons, and I cannot make it work when

Re: [Numpy-discussion] Numpy 1.1.1 release notes.

2008-07-31 Thread Pauli Virtanen
Thu, 31 Jul 2008 12:12:54 -0600, Charles R Harris wrote: Hi All, I've attached draft release notes for Numpy 1.1.1. If you have anything to add or correct, let me know. [clip] Bug fixes #854, r5456? -- Pauli Virtanen ___ Numpy-discussion

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread David Cournapeau
hot -- it takes about 10 cold. I've been wondering about that. time python -c import numpy real0m8.383s user0m0.320s sys 0m7.805s and similar results if run multiple times in a row. What does python -c import sys; print sys.path say ? Any idea what could be wrong? I have

Re: [Numpy-discussion] Numpy 1.1.1 release notes.

2008-07-31 Thread Charles R Harris
On Thu, Jul 31, 2008 at 12:23 PM, Pauli Virtanen [EMAIL PROTECTED] wrote: Thu, 31 Jul 2008 12:12:54 -0600, Charles R Harris wrote: Hi All, I've attached draft release notes for Numpy 1.1.1. If you have anything to add or correct, let me know. [clip] Bug fixes #854, r5456?

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Gael Varoquaux
On Thu, Jul 31, 2008 at 10:12:22AM -0700, Christopher Barker wrote: I've been wondering about that. time python -c import numpy real0m8.383s user0m0.320s sys 0m7.805s I don't know what is wrong, but this is plain wrong, unless you are on a distant file system, or something

Re: [Numpy-discussion] Numpy 1.1.1 release notes.

2008-07-31 Thread Pierre GM
Chuck, Can you remove the entry Pierre GM -- masked array, improved support for flexible dtypes. from General Improvements ? The work was done for 1.2 and not completely backported, so that's not really a lot of improvements. It will for 1.2, however: when is this one supposed to be released ?

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Scott Ransom
On Thu, Jul 31, 2008 at 07:46:20AM -0500, Nathan Bell wrote: On Thu, Jul 31, 2008 at 7:31 AM, Hanni Ali [EMAIL PROTECTED] wrote: I would just to highlight an alternate use of numpy to interactive use. We have a cluster of machines which process tasks on an individual basis where a master

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread Robert Kern
On Thu, Jul 31, 2008 at 05:43, Andrew Dalke [EMAIL PROTECTED] wrote: On Jul 31, 2008, at 12:03 PM, Robert Kern wrote: But you still can't remove them since they are being used inside numerictypes. That's why I labeled them internal utility functions instead of leaving them with minimal

Re: [Numpy-discussion] distutils and inplace build: is numpy supposed to work ?

2008-07-31 Thread Robert Kern
On Thu, Jul 31, 2008 at 09:18, David Cournapeau [EMAIL PROTECTED] wrote: Hi, I wanted to know if numpy was supposed to work when built in place through the -i option of distutils. The reason why I am asking it that I would like to support it in numscons, and I cannot make it work when

Re: [Numpy-discussion] import numpy is slow

2008-07-31 Thread David Cournapeau
On Fri, Aug 1, 2008 at 5:02 AM, Robert Kern [EMAIL PROTECTED] wrote: 5) Proxy objects ... I would really like to avoid proxy objects. They have caused fragility in the past. One recurrent problem around import times optimization is that it is some work to improve it, but it takes one line to

[Numpy-discussion] patches to reduce import costs

2008-07-31 Thread Andrew Dalke
I don't see a place to submit patches. Is there a patch manager for numpy? Here's a patch to defer importing 'tempfile' until needed. I previously mentioned one other place that didn't need tempfile. With this there is no 'import tempfile' during 'import numpy' This improves startup by