On Jul 1, 2008, at 2:22 AM, Robert Kern wrote:
> Your use case isn't so typical and so suffers on the import time
> end of the
> balance.
I'm working on my presentation for EuroSciPy. "Isn't so typical"
seems to be a good summary of my first slide. :)
>> Any chance of cutting down on the nu
On Mon, Jun 30, 2008 at 18:32, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> (Trying again now that I'm subscribed. BTW, there's no link to the
> subscription page from numpy.scipy.org .)
>
>
> The initial 'import numpy' loads a huge number of modules, even when
> I don't need them.
>
> Python 2.5 (r2
(Trying again now that I'm subscribed. BTW, there's no link to the
subscription page from numpy.scipy.org .)
The initial 'import numpy' loads a huge number of modules, even when
I don't need them.
Python 2.5 (r25:51918, Sep 19 2006, 08:49:13)
[GCC 4.0.1 (Apple Computer, Inc. build 5341)] on
Hi all,
this is just a reminder, in case you'll be attending the SIAM 2008
annual meeting next week in San Diego, that there will be a 3-part
minisymposium focusing on the uses of Python and Sage in scientific
computing:
http://meetings.siam.org/sess/dsp_programsess.cfm?SESSIONCODE=7369
http://me
On Mon, Jun 30, 2008 at 14:06, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 30, 2008 at 2:55 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> Add the doctests argument.
>
> Where is the buildbot configuration kept?
I have not the slightest idea. Stéfan?
--
Robert Kern
"I have come to bel
On Mon, Jun 30, 2008 at 2:55 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> Add the doctests argument.
Where is the buildbot configuration kept?
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-d
On Mon, Jun 30, 2008 at 13:38, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> It seems to me that the buildbots should be running the doctests in
> addition to the unit tests, but right now the buildbot test command
> "numpy.test(level=,verbosity=)" doesn't do that. We could
> eith
Hi all,
It seems to me that the buildbots should be running the doctests in
addition to the unit tests, but right now the buildbot test command
"numpy.test(level=,verbosity=)" doesn't do that. We could
either add "doctests=True" to the buildbot test command, or make
"level" above some thr
Hi all,
I can commit any/all of the following changes as long as they are
agreeable to everybody:
1. All doctests in NumPy will have the numpy module available in their
execution context as "np".
2. Turn on the normalized whitespace option for all doctests. Having
a doctest fail just because th
On Mon, Jun 30, 2008 at 12:17, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> While I was working on the doctest tweaks, I ran across a doctest that
> failed because tensorsolve uses a function "wrap" that's not defined.
> It seems that I should make the following change to fix it (at the
> start of te
While I was working on the doctest tweaks, I ran across a doctest that
failed because tensorsolve uses a function "wrap" that's not defined.
It seems that I should make the following change to fix it (at the
start of tensorsolve's code) :
-a = asarray(a)
+a,wrap = _makearray(a)
Doing so s
11 matches
Mail list logo
