I realise this, but 1659 tests in 8.739s with Nose as opposed to just
over 1000 tests in right around 1 second with the previous test system
means there is some kind of slowdown involved besides just the number
of tests being found. Not that I mind: I'm not looking for blazing
speed when running te
On Thu, Jun 19, 2008 at 11:59, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 5:24 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>>> - The signature of numpy.test in 1.2 will be backward compatible with
>>> 1.1, and it will at least return some indication of failure (if not
>>> the
On Wed, Jun 18, 2008 at 5:24 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> - The signature of numpy.test in 1.2 will be backward compatible with
>> 1.1, and it will at least return some indication of failure (if not
>> the same object as in 1.1). This will, by the way, make it different
>> from th
2008/6/19 Joshua Lippai <[EMAIL PROTECTED]>:
> The new testing system works well over here, built on Mac OS X 10.5.2
> with GCC 4.2. No errors/failures, but there is that warning Charles
> mentioned as well as the noticeable difference in speed between this
> and the old tests.
Nose does a more th
The new testing system works well over here, built on Mac OS X 10.5.2
with GCC 4.2. No errors/failures, but there is that warning Charles
mentioned as well as the noticeable difference in speed between this
and the old tests.
Josh
On Mon, Jun 16, 2008 at 8:28 PM, Alan McIntyre <[EMAIL PROTECTED]>
On Wed, Jun 18, 2008 at 16:12, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 4:15 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> We've been already been making that warning for some time now, in the
>> proper venues. warning.warn() is good for DeprecationWarnings, but not
>> thi
On Wed, Jun 18, 2008 at 4:15 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> We've been already been making that warning for some time now, in the
> proper venues. warning.warn() is good for DeprecationWarnings, but not
> this. We are good to go for nose being used in 1.2.
Ok, so somebody tell me if
Stéfan van der Walt wrote:
> 2008/6/18 Alan McIntyre <[EMAIL PROTECTED]>:
>
>> Is "next release" referring to 1.2 or the release after that? If it's
>> the release after 1.2, then I assume that 1.2 must still be able to
>> run all its tests without nose.
>>
>
> Alternatively, we could dist
On Wed, Jun 18, 2008 at 13:42, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 12:05 PM, Stéfan van der Walt <[EMAIL PROTECTED]>
> wrote:
>> a) Warn that Nose is becoming a dependency (next release).
>
> Is "next release" referring to 1.2 or the release after that? If it's
> th
On Wed, Jun 18, 2008 at 10:42, Anne Archibald <[EMAIL PROTECTED]> wrote:
> 2008/6/17 Alan McIntyre <[EMAIL PROTECTED]>:
>> You can replace ParametricTest with generators, as described here:
>> http://scipy.org/scipy/scipy/wiki/TestingGuidelines
>
> Hmm. This won't work with the current version
2008/6/18 Alan McIntyre <[EMAIL PROTECTED]>:
> Is "next release" referring to 1.2 or the release after that? If it's
> the release after 1.2, then I assume that 1.2 must still be able to
> run all its tests without nose.
Alternatively, we could distribute Nose inside of NumPy for one
release? I
On Wed, Jun 18, 2008 at 12:05 PM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> a) Warn that Nose is becoming a dependency (next release).
Is "next release" referring to 1.2 or the release after that? If it's
the release after 1.2, then I assume that 1.2 must still be able to
run all its tests
2008/6/18 Stéfan van der Walt <[EMAIL PROTECTED]>:
> 2008/6/18 Anne Archibald <[EMAIL PROTECTED]>:
>> Well, probably. But more so for those that are used widely throughout
>> numpy itself, since many of us learn how to write code using numpy by
>> reading numpy source. (Yes, this means that "intern
On Wed, Jun 18, 2008 at 11:42 AM, Anne Archibald
<[EMAIL PROTECTED]> wrote:
>> You can replace ParametricTest with generators, as described here:
>> http://scipy.org/scipy/scipy/wiki/TestingGuidelines
>
> Hmm. This won't work with the current version of numpy, will it? That
> is, it needs nose.
2008/6/18 Anne Archibald <[EMAIL PROTECTED]>:
> Well, probably. But more so for those that are used widely throughout
> numpy itself, since many of us learn how to write code using numpy by
> reading numpy source. (Yes, this means that "internal" conventions
> like "numpy.core.whatever" get used by
2008/6/17 Alan McIntyre <[EMAIL PROTECTED]>:
> On Tue, Jun 17, 2008 at 8:15 PM, Anne Archibald
> <[EMAIL PROTECTED]> wrote:
>> Uh, I assumed NumpyTestCase was public and used it. I'm presumably not
>> alone, so perhaps a deprecation warning would be good. What
>> backward-compatible class should I
On Tue, Jun 17, 2008 at 22:44, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> I'm assuming this experience should tell me that any item "bar" that I
> can get by issuing "from numpy.foo import bar" should be considered
> the public API and therefore deprecated instead of removed? ;)
It's usually a go
On Mon, Jun 16, 2008 at 8:39 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> Please port over the changes I made to scipy.testing in scipy's r4424
> in order to avoid importing nose until the actual execution of tests.
By the way, I notice that making those changes broke the ability to
run a single t
On Tue, Jun 17, 2008 at 8:26 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 17, 2008 at 09:53, Alan McIntyre <[EMAIL PROTECTED]> wrote:
>> If there's a consensus that they need to go back in and get marked as
>> deprecated, I'll put them back.
>
> Yes, please do this.
Using numpy.depreca
On Tue, Jun 17, 2008 at 8:15 PM, Anne Archibald
<[EMAIL PROTECTED]> wrote:
> Uh, I assumed NumpyTestCase was public and used it. I'm presumably not
> alone, so perhaps a deprecation warning would be good. What
> backward-compatible class should I use? unittest.TestCase?
Yes, unittest.TestCase seem
2008/6/17 Anne Archibald <[EMAIL PROTECTED]>:
> 2008/6/17 Alan McIntyre <[EMAIL PROTECTED]>:
> > On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]>
> wrote:
> >> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am
> >> wondering whether these classes part of the publ
On Tue, Jun 17, 2008 at 09:53, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> wrote:
>> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am
>> wondering whether these classes part of the public interface or were they
>> r
2008/6/17 Alan McIntyre <[EMAIL PROTECTED]>:
> On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> wrote:
>> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am
>> wondering whether these classes part of the public interface or were they
>> reserved for internal usage
On Tue, June 17, 2008 6:17 am, Robert Kern wrote:
> On Mon, Jun 16, 2008 at 21:18, Alan McIntyre <[EMAIL PROTECTED]>
> wrote:
>> On Mon, Jun 16, 2008 at 9:04 PM, Charles R Harris
>> <[EMAIL PROTECTED]> wrote:
>
>>> In [1]: numpy.test()
>>> Not implemented: Defined_Binary_Op
>>> Not implemented: Def
On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> wrote:
> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am
> wondering whether these classes part of the public interface or were they
> reserved for internal usage ?
>
> In the former, it might be well to deprecate
On Mon, Jun 16, 2008 at 11:17 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> These files were for the in-development g3 version of f2py. That
> development has moved outside of numpy, so I think they can be removed
> wholesale. Some of them seem to require a Fortran 90 compiler, so I
> have had them
I noticed that NumpyTest and NumpyTestCase disappeared, and now I am
wondering whether these classes part of the public interface or were they
reserved for internal usage ?
In the former, it might be well to deprecate them before removing them.
Cheers,
David
2008/6/17 David Cournapeau <[EMAIL P
David Cournapeau wrote:
> It does not work with python2.6a3, but it is a nose problem, apparently
> (I have the exact same error)
>
Sorry, it is a python26 problem, not nose.
cheers,
David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.or
Alan McIntyre wrote:
> Hi all,
>
> I just checked in the switch to use nose to run unit tests. Please
> let me know if you experience any difficulties as a result.
>
It does not work with python2.6a3, but it is a nose problem, apparently
(I have the exact same error)
http://bzimmer.ziclix.co
On Mon, Jun 16, 2008 at 21:18, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 16, 2008 at 9:04 PM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
>> In [1]: numpy.test()
>> Not implemented: Defined_Binary_Op
>> Not implemented: Defined_Binary_Op
>> Defined_Operator not defined used by Gener
On Mon, Jun 16, 2008 at 8:18 PM, Alan McIntyre <[EMAIL PROTECTED]>
wrote:
> On Mon, Jun 16, 2008 at 9:04 PM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> > Did you add any documentation to the readme? Any particular version
> > dependency for Nose?
>
> I did update README.txt, but I forgot to p
On Mon, Jun 16, 2008 at 9:04 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> Did you add any documentation to the readme? Any particular version
> dependency for Nose?
I did update README.txt, but I forgot to put the minimum Nose version
in there; thanks for mentioning that. I just checked in a
On Mon, Jun 16, 2008 at 8:39 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 16, 2008 at 19:28, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> Please port over the changes I made to scipy.testing in scipy's r4424
> in order to avoid importing nose until the actual execution of tests.
Done in
On Mon, Jun 16, 2008 at 6:28 PM, Alan McIntyre <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I just checked in the switch to use nose to run unit tests. Please
> let me know if you experience any difficulties as a result.
>
Did you add any documentation to the readme? Any particular version
dependenc
On Mon, Jun 16, 2008 at 19:28, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I just checked in the switch to use nose to run unit tests. Please
> let me know if you experience any difficulties as a result.
Please port over the changes I made to scipy.testing in scipy's r4424
in order to
Hi all,
I just checked in the switch to use nose to run unit tests. Please
let me know if you experience any difficulties as a result.
Thanks,
Alan
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/
36 matches
Mail list logo