On Wed, Jun 18, 2008 at 9:54 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 23:48, Fernando Perez <[EMAIL PROTECTED]> wrote:
>> Stefan, core team?
>
> Knock yourself out.
Thanks. Committed in r5298.
Cheers,
f
___
Numpy-discussion
On Wed, Jun 18, 2008 at 23:48, Fernando Perez <[EMAIL PROTECTED]> wrote:
> Stefan, core team?
Knock yourself out.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlyi
Hi all,
after I updated the pyrex code to use cython, a bit of confusion led
me to using .pxi includes instead of .pxd files and cimport. That
turned out to be mistaken, as later clarified by the Cython team:
http://codespeak.net/pipermail/cython-dev/2008-April/000628.html
Would anyone object t
Thanks for pointing them out. I will look into both of them. I like
the "with" statement. From an implementation perspective, the "with"
statement looks simpler since the Python parser seems to discard
comments and I use the Python parser as front end for compiler.
For other annotations, I h
Hello,
I am looking for some pointers that will hopefully get me a round an issue I
have hit.
I have a timeseries of river flow and would like to carry out some analysis on
the recession periods. That is anytime the values are decreasing. I would
like to restrict (mask) my data to any values
2008/6/18 Rahul Garg <[EMAIL PROTECTED]>:
> I want to add a similar annotation to Python
> example usage :
>
> "pragma parallel for"
> for i in xrange(m): a[i] = b[i]*c[i]
>
> The interpreter ignores such strings and the code will of course
> execute serially but such strings can potentially be use
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
On Wed, Jun 18, 2008 at 11:48 AM, Anne Archibald <[EMAIL PROTECTED]>
wrote:
> 2008/6/18 Stéfan van der Walt <[EMAIL PROTECTED]>:
> > 2008/6/18 Anne Archibald <[EMAIL PROTECTED]>:
> >> In [7]: x.take(x.argsort())
> >> Out[7]: array([ 0. , 0.1, 0.2, 0.3])
> >>
> >> If you would like to think of i
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
2008/6/18 Stéfan van der Walt <[EMAIL PROTECTED]>:
> 2008/6/18 Anne Archibald <[EMAIL PROTECTED]>:
>> In [7]: x.take(x.argsort())
>> Out[7]: array([ 0. , 0.1, 0.2, 0.3])
>>
>> If you would like to think of it more mathematically, when you feed
>> np.argsort() an array that represents a permutati
On Tue, Jun 17, 2008 at 7:38 AM, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> Where do we keep the buildbot configuration? The arguments for
> numpy.test have changed with the switch to nose, so the test step
> fails. It also appears nose needs to be installed/updated on the
> build slaves.
Eh, ple
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.
On Wed, Jun 18, 2008 at 10:53 AM, Stéfan van der Walt <[EMAIL PROTECTED]>
wrote:
> 2008/6/18 Anne Archibald <[EMAIL PROTECTED]>:
> > In [7]: x.take(x.argsort())
> > Out[7]: array([ 0. , 0.1, 0.2, 0.3])
> >
> > If you would like to think of it more mathematically, when you feed
> > np.argsort()
Alan McIntyre wrote:
> On Wed, Jun 18, 2008 at 12:21 PM, Christopher Hanley <[EMAIL PROTECTED]>
> wrote:
>> I have received the following message from our system guru here at STScI
>> regarding the recent changes to the way testing is done with nose. The
>> automated scripts he was using to monit
On Wed, Jun 18, 2008 at 12:21 PM, Christopher Hanley <[EMAIL PROTECTED]> wrote:
> I have received the following message from our system guru here at STScI
> regarding the recent changes to the way testing is done with nose. The
> automated scripts he was using to monitor the success or failure of
Thanks, Anne. I misinterpreted what argsort() provides. I was
thinking about it in terms of the kind of behaviour exhibited by
searchsorted(). --Tom
--
On 18-Jun-08, at 12:10 PM, Anne Archibald wrote:
> 2008/6/18 Thomas J. Duck <[EMAIL PROTECTED]>:
>
>> I have found what I
2008/6/18 Anne Archibald <[EMAIL PROTECTED]>:
> In [7]: x.take(x.argsort())
> Out[7]: array([ 0. , 0.1, 0.2, 0.3])
>
> If you would like to think of it more mathematically, when you feed
> np.argsort() an array that represents a permutation of the numbers
> 0,1,...,n-1, you get back the inverse
Hi,
I have received the following message from our system guru here at STScI
regarding the recent changes to the way testing is done with nose. The
automated scripts he was using to monitor the success or failure of
numpy builds is now broken. Below is his message:
The new numpy test interfa
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
Hi.
I have been working on a Python to C compiler called unPython (updates
coming tomorow). One of the features I want to work on is parallel
loop annotations similar to OpenMP for C. Given the multicore
revolution, and given the lack of real concurrency in CPython, such a
feature will be
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
2008/6/18 Dinesh B Vadhia <[EMAIL PROTECTED]>:
> Say, there are two initialized numpy arrays:
It is somewhat misleading to think of numpy arrays as "initialized" or
"uninitialized". All numpy arrays are dynamically allocated, and under
many circumstances they are given their values on creation.
>
2008/6/18 Thomas J. Duck <[EMAIL PROTECTED]>:
> I have found what I think is some strange behavior for argsort
> () and take(). First, here is an example that works as expected:
>
> >>> x = numpy.array([1,0,3,2])
> >>> x.argsort()
> array([1, 0, 3, 2])
>
> argsort() returns th
Hi there,
looks like it, moving from gcc3.3.4 to gcc4.1.2 seems to have fix it.
Thx,
C.
David Cournapeau wrote:
> Charles Doutriaux wrote:
>
>> Hello,
>>
>> I'm trying to build 1.1.0 on a:
>> Linux thunder0 2.6.9-74chaos #1 SMP Wed Oct 24 08:41:12 PDT 2007 ia64
>> ia64 ia64 GNU/Linux
>>
>>
Well this got nothing to do with cdat 5.0 yet. At this point it just
built python from sources, and is putting numpy 1.1.0 in it.
I'll check the compiler bug option next... What if it is indeed a
compiler bug? What to do next?
C.
Charles R Harris wrote:
>
>
> On Tue, Jun 17, 2008 at 3:40 PM, C
Hi,
I have found what I think is some strange behavior for argsort
() and take(). First, here is an example that works as expected:
>>> x = numpy.array([1,0,3,2])
>>> x.argsort()
array([1, 0, 3, 2])
argsort() returns the original array, which is self-indexing for
numb
34 matches
Mail list logo
