On Sun, Dec 21, 2008 at 11:37 PM, wrote:
> On Sun, Dec 21, 2008 at 11:10 PM, Pierre GM wrote:
>>
>> On Dec 21, 2008, at 10:19 PM, josef.p...@gmail.com wrote:
>>>
From the examples that I tried out np.sort, sorts each column
>>> separately (with axis = 0). If the elements of a row is suppose
On Sun, Dec 21, 2008 at 11:10 PM, Pierre GM wrote:
>
> On Dec 21, 2008, at 10:19 PM, josef.p...@gmail.com wrote:
>>
>>> From the examples that I tried out np.sort, sorts each column
>> separately (with axis = 0). If the elements of a row is supposed to
>> stay together, then np.sort doesn't work
>
On Dec 21, 2008, at 10:19 PM, josef.p...@gmail.com wrote:
>
>> From the examples that I tried out np.sort, sorts each column
> separately (with axis = 0). If the elements of a row is supposed to
> stay together, then np.sort doesn't work
Well, if the elements are supposed to stay together, why wo
josef.p...@gmail.com wrote:
>> I may miss something obvious, but why are you using lexsort at all ? At
>> leat, the first example is easily achieved with sort(x, axis=0) - but
>> maybe you have more complicated examples in mind where you need actual
>> lexical sort:
>>
>> David
>>
>
> >From th
>
> I may miss something obvious, but why are you using lexsort at all ? At
> leat, the first example is easily achieved with sort(x, axis=0) - but
> maybe you have more complicated examples in mind where you need actual
> lexical sort:
>
> David
>From the examples that I tried out np.sort, sorts
On Sun, Dec 21, 2008 at 20:53, David Cournapeau
wrote:
> josef.p...@gmail.com wrote:
>> I was looking for a function that sorts a 2-dimensional array by rows.
>> That's what I came up with, is there a more direct way?
>>
> a
>> array([[1, 2],
>>[0, 0],
>>[1, 0],
>>[0, 2
josef.p...@gmail.com wrote:
> I was looking for a function that sorts a 2-dimensional array by rows.
> That's what I came up with, is there a more direct way?
>
a
> array([[1, 2],
>[0, 0],
>[1, 0],
>[0, 2],
>[2, 1],
>[1, 0],
>[1, 0],
>[0,
On Mon, Dec 22, 2008 at 3:10 AM, Pauli Virtanen wrote:
> Mon, 22 Dec 2008 00:30:55 +0900, David Cournapeau wrote:
>
>> On Sun, Dec 21, 2008 at 11:42 PM, Pauli Virtanen wrote:
>>> Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote: [clip]
Is everything under trunk/doc necessary to bu
I was looking for a function that sorts a 2-dimensional array by rows.
That's what I came up with, is there a more direct way?
>>> a
array([[1, 2],
[0, 0],
[1, 0],
[0, 2],
[2, 1],
[1, 0],
[1, 0],
[0, 0],
[1, 0],
[2, 2]])
>>> a[np.lexso
Mon, 22 Dec 2008 00:30:55 +0900, David Cournapeau wrote:
> On Sun, Dec 21, 2008 at 11:42 PM, Pauli Virtanen wrote:
>> Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote: [clip]
>>> Is everything under trunk/doc necessary to build the doc ? Or only
>>> a
>>> subset of it ?
>>
>> Only
On Fri, Dec 19, 2008 at 4:30 PM, Ondrej Certik wrote:
> while packaging the new version of numpy, I realized that it is
> missing a documentation. I just checked with Stefan on Jabber and he
> thinks
> it should be rather a trivial fix. Do you Jarrod think you could
> please release a new tarball
On Sun, Dec 21, 2008 at 11:42 PM, Pauli Virtanen wrote:
> Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote:
> [clip]
>> Is everything under trunk/doc necessary to build the doc ? Or only a
>> subset of it ?
>
> Only a subset: Makefile, postprocess.py, release/*, source/*, and
> sphinxex
Sun, 21 Dec 2008 22:48:41 +0900, David Cournapeau wrote:
[clip]
> Is everything under trunk/doc necessary to build the doc ? Or only a
> subset of it ?
Only a subset: Makefile, postprocess.py, release/*, source/*, and
sphinxext/*.
The rest is some older material (eg. numpybook/*), stuff targ
Pauli Virtanen wrote:
> Sun, 21 Dec 2008 13:05:57 +0100, Ondrej Certik wrote:
>
>
>> On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
>>
>>> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
>>>
On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik
wrote:
On Sun, Dec 21, 2008 at 1:49 PM, Pauli Virtanen wrote:
> Sun, 21 Dec 2008 13:05:57 +0100, Ondrej Certik wrote:
>
>> On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
>>> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik
wrote:
Sun, 21 Dec 2008 13:05:57 +0100, Ondrej Certik wrote:
> On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
>> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
>>> On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik
>>> wrote:
Just to make it clear -- I think the docs should not be ge
Ondrej Certik wrote:
>
> Why not to just include the *sources* together with numpy, and
> possibly include html+whatever in a separate documentation package?
>
I don't think having separate built doc and built package is a good
idea. It is confusing for the user, and I am afraid we won't alway
On Sat, Dec 20, 2008 at 3:02 PM, Pauli Virtanen wrote:
> Sat, 20 Dec 2008 20:15:43 +0900, David Cournapeau wrote:
>> On Sat, Dec 20, 2008 at 7:43 PM, Ondrej Certik wrote:
>>> Just to make it clear -- I think the docs should not be generated in
>>> the tarball -- only the sources should be there.
On Sun, Dec 21, 2008 at 12:13 AM, David Cournapeau
wrote:
>Just a few words to mention that I've finally managed to build numpy
> with the mingw-w64 project (port of mingw to AMD 64 bits MS OS), and it
> almost run OK.
Thanks for working on this.
Jarrod
___
On Sun, Dec 21, 2008 at 05:13:11PM +0900, David Cournapeau wrote:
> Just a few words to mention that I've finally managed to build numpy
> with the mingw-w64 project
I know it was a tough task. Thanks a lot for doing this.
Gaël
___
Numpy-discussion
Hi,
Just a few words to mention that I've finally managed to build numpy
with the mingw-w64 project (port of mingw to AMD 64 bits MS OS), and it
almost run OK. By almost, I mean that numpy.test() finishes without
crash, assuming a few unit tests are skipped (some long double
problems). Not all
21 matches
Mail list logo
