Re: [Numpy-discussion] Numpy discussion - was: Raveling, reshape order keyword unnecessarily confuses index and memory ordering

2013-04-07 Thread Paul Ivanov
Matthew Brett, on 2013-04-06 10:39, wrote: > Hi, > > On Sat, Apr 6, 2013 at 10:18 AM, matti picus wrote: > > as a lurker, may I say that this discussion seems to have become > > non-productive? > > Well - the discussion is about two things - as so often the case on numpy. > > The first is abou

Re: [Numpy-discussion] Sort performance with structured array

2013-04-07 Thread Charles R Harris
On Sun, Apr 7, 2013 at 5:56 PM, Charles R Harris wrote: > > > On Sun, Apr 7, 2013 at 5:23 PM, Tom Aldcroft < > aldcr...@head.cfa.harvard.edu> wrote: > >> I'm seeing about a factor of 50 difference in performance between >> sorting a random integer array versus sorting that same array viewed >> as

Re: [Numpy-discussion] Sort performance with structured array

2013-04-07 Thread Charles R Harris
On Sun, Apr 7, 2013 at 5:23 PM, Tom Aldcroft wrote: > I'm seeing about a factor of 50 difference in performance between > sorting a random integer array versus sorting that same array viewed > as a structured array. Am I doing anything wrong here? > > In [2]: x = np.random.randint(1, size=100

[Numpy-discussion] Sort performance with structured array

2013-04-07 Thread Tom Aldcroft
I'm seeing about a factor of 50 difference in performance between sorting a random integer array versus sorting that same array viewed as a structured array. Am I doing anything wrong here? In [2]: x = np.random.randint(1, size=1) In [3]: xarr = x.view(dtype=[('a', np.int)]) In [4]: tim

Re: [Numpy-discussion] [numfocus] Growing the contributor base of Numpy

2013-04-07 Thread huangkan...@gmail.com
That's awesome. I'm definitely one of the targeted audience. Thanks. On Sun, Apr 7, 2013 at 5:40 PM, David Cournapeau wrote: > I have prepared a preliminary proposal > https://github.com/enthought/davidc-scipy-2013/blob/master/proposal.rst > > Roughly, after ensuring everybody knows how to buil

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Steve Waterbury
On 04/07/2013 05:59 PM, Nathaniel Smith wrote: > On Sun, Apr 7, 2013 at 10:49 PM, Olivier Delalleau wrote: >> 2013/4/7 >>> >>> On Sun, Apr 7, 2013 at 5:34 PM, Steve Waterbury >>> wrote: On 04/07/2013 05:30 PM, Nathaniel Smith wrote: > On Sun, Apr 7, 2013 at 10:25 PM, Steve Waterbury >>>

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Nathaniel Smith
On Sun, Apr 7, 2013 at 10:49 PM, Olivier Delalleau wrote: > 2013/4/7 >> >> On Sun, Apr 7, 2013 at 5:34 PM, Steve Waterbury >> wrote: >> > On 04/07/2013 05:30 PM, Nathaniel Smith wrote: >> >> On Sun, Apr 7, 2013 at 10:25 PM, Steve Waterbury >> >> wrote: >> >>> On 04/07/2013 05:02 PM, Chris Barke

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Olivier Delalleau
2013/4/7 > On Sun, Apr 7, 2013 at 5:34 PM, Steve Waterbury > wrote: > > On 04/07/2013 05:30 PM, Nathaniel Smith wrote: > >> On Sun, Apr 7, 2013 at 10:25 PM, Steve Waterbury > >> wrote: > >>> On 04/07/2013 05:02 PM, Chris Barker - NOAA Federal wrote: > On Sun, Apr 7, 2013 at 8:06 AM, Daπid

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread josef . pktd
On Sun, Apr 7, 2013 at 5:34 PM, Steve Waterbury wrote: > On 04/07/2013 05:30 PM, Nathaniel Smith wrote: >> On Sun, Apr 7, 2013 at 10:25 PM, Steve Waterbury >> wrote: >>> On 04/07/2013 05:02 PM, Chris Barker - NOAA Federal wrote: On Sun, Apr 7, 2013 at 8:06 AM, Daπid wrote: > On 7 April

Re: [Numpy-discussion] [numfocus] Growing the contributor base of Numpy

2013-04-07 Thread David Cournapeau
I have prepared a preliminary proposal https://github.com/enthought/davidc-scipy-2013/blob/master/proposal.rst Roughly, after ensuring everybody knows how to build numpy from sources in a dev-friendly way, I was thinking about - describing the source code tree organization - talk about the main

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Steve Waterbury
On 04/07/2013 05:30 PM, Nathaniel Smith wrote: > On Sun, Apr 7, 2013 at 10:25 PM, Steve Waterbury > wrote: >> On 04/07/2013 05:02 PM, Chris Barker - NOAA Federal wrote: >>> On Sun, Apr 7, 2013 at 8:06 AM, Daπid wrote: On 7 April 2013 16:53, Happyman wrote: >>> $pip install numpy # to i

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Nathaniel Smith
On Sun, Apr 7, 2013 at 10:25 PM, Steve Waterbury wrote: > On 04/07/2013 05:02 PM, Chris Barker - NOAA Federal wrote: >> On Sun, Apr 7, 2013 at 8:06 AM, Daπid wrote: >>> On 7 April 2013 16:53, Happyman wrote: >> >>> $pip install numpy # to install package "numpy" >> >> as a warning, last I checke

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Steve Waterbury
On 04/07/2013 05:02 PM, Chris Barker - NOAA Federal wrote: > On Sun, Apr 7, 2013 at 8:06 AM, Daπid wrote: >> On 7 April 2013 16:53, Happyman wrote: > >> $pip install numpy # to install package "numpy" > > as a warning, last I checked pip did not support binary installs ... Guess you didn't chec

Re: [Numpy-discussion] question about the data entry in the __array_interface__

2013-04-07 Thread Nathaniel Smith
On Sun, Apr 7, 2013 at 2:26 PM, Valentin Haenel wrote: > I know that the address is contained in the 'data' field of the > '__array_interface__' and is either an int or a long. My guess is that > this depends on the architecture of the system, i.e. 32 vs 64 bit > systems. > > My question is: what

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Chris Barker - NOAA Federal
On Sun, Apr 7, 2013 at 8:06 AM, Daπid wrote: > On 7 April 2013 16:53, Happyman wrote: > $pip install numpy # to install package "numpy" as a warning, last I checked pip did not support binary installs, and you really want a binary installer for numpy/scipy, unless you've got your development en

Re: [Numpy-discussion] converting "numpy.bytes_" from numpy 1.7.0 to "numpy.string_" of numpy 1.6.1

2013-04-07 Thread Chris Barker - NOAA Federal
On Sun, Apr 7, 2013 at 11:28 AM, Sergio Rojas wrote: > I am using a function which under python 2.2.7 and numpy 1.6.1 > returns a "list" (called d) whose elements are of type > "numpy.string_" (see below). > > Under python 3.3.0 and numpy 1.7.0 the same function returns the > list as an object of

Re: [Numpy-discussion] question about the data entry in the __array_interface__

2013-04-07 Thread Chris Barker - NOAA Federal
On Sun, Apr 7, 2013 at 6:26 AM, Valentin Haenel wrote: > I am currently working with a C extension that wraps a C library. > > The library contains a function that takes, amongst others, a 'void *' > as an argument. Now, I would like for that function to be able to read > the 'data' buffer of a nu

[Numpy-discussion] ANN: SciPy 0.12.0 release

2013-04-07 Thread Ralf Gommers
We are pleased to announce the availability of SciPy 0.12.0. This release has some cool new features (see highlights below) and a large amount of bug fixes and maintenance work under the hood. The number of contributors also keeps rising steadily - 75 people contributed patches to this release. We

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Eric Carlson
Hello, For most people who want to be doing amazing things through python with little fuss, you'd probably be better off downloading a comprehensive distribution that includes many useful modules. Some examples of several - For windows: Pythonxy - http://code.google.com/p/pythonxy/wiki/Downloads

[Numpy-discussion] converting "numpy.bytes_" from numpy 1.7.0 to "numpy.string_" of numpy 1.6.1

2013-04-07 Thread Sergio Rojas
Dear all, I am using a function which under python 2.2.7 and numpy 1.6.1 returns a "list" (called d) whose elements are of type "numpy.string_" (see below). Under python 3.3.0 and numpy 1.7.0 the same function returns the list as an object of type "builtins.list" whose elements are of type "nump

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Colin J. Williams
On 07/04/2013 10:32 AM, Happyman wrote: Hello, I started using python 4-5 months ago. At that time I didn't realize there are incredibly many resource like modules, additional programs (ready one) in python. The problem is to which one

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Daπid
On 7 April 2013 16:53, Happyman wrote: > I completed my Registration..but still no idea how to use it..it is ,may > be, lack of experience of python .. > You don't need registration. The easiest way to use it is via pip or easy_install. If you are on Windows, download and execute the easy_instal

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Happyman
thanks Oliver I completed my Registration..but still no idea how to use it..it is ,may be, lack of experience of python .. could you show the basic steps?? Воскресенье, 7 апреля 2013, 10:41 -04:00 от Olivier Delalleau : >The Python Package Index ( https://pypi.python.org/pypi ) is to my know

Re: [Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Olivier Delalleau
The Python Package Index (https://pypi.python.org/pypi) is to my knowledge the largest centralized source of Python packages. That's where easy_install and pip typically fetch them so that you can install from the command line without manual download. -=- Olivier 2013/4/7 Happyman > Hello, > >

[Numpy-discussion] Sources more confusing in Python

2013-04-07 Thread Happyman
Hello, I started using python 4-5 months ago. At that time I didn't realize there are incredibly many resource like modules, additional programs (ready one) in python. The problem is to which one I can get all I want "properly". I mean where (exact place) I can download standard modules withou

Re: [Numpy-discussion] question about the data entry in the __array_interface__

2013-04-07 Thread Pauli Virtanen
07.04.2013 16:26, Valentin Haenel kirjoitti: [clip] > My question is: what is the correct type to use when using > PyArg_ParseTuple to convert the value. [clip] This is probably the most correct option: http://docs.python.org/2/c-api/long.html#PyLong_AsVoidPtr Not via ParseTuple, though. -- P

[Numpy-discussion] question about the data entry in the __array_interface__

2013-04-07 Thread Valentin Haenel
Hi, I am currently working with a C extension that wraps a C library. The library contains a function that takes, amongst others, a 'void *' as an argument. Now, I would like for that function to be able to read the 'data' buffer of a numpy array and thus need to pass address from Python down int

Re: [Numpy-discussion] ANN: NumPy 1.7.1 release

2013-04-07 Thread Ralf Gommers
On Sun, Apr 7, 2013 at 11:40 AM, Colin J. Williams wrote: > On 07/04/2013 4:09 AM, Ondřej Čertík wrote: > > [snip] > P.S. I'll create the Mac binary installers in a few days. Pypi is updated. > > > > [snip] > > Ondřej, > > I've seen the PyPi version *criticized on the grounds that it makes no >

Re: [Numpy-discussion] ANN: NumPy 1.7.1 release

2013-04-07 Thread Colin J. Williams
On 07/04/2013 4:09 AM, Ondřej Čertík wrote: [snip] P.S. I'll create the Mac binary installers in a few days. Pypi is updated. [snip] Ondřej, I've seen the PyPi version criticized on the grounds that it makes no

Re: [Numpy-discussion] ANN: NumPy 1.7.1rc1 release

2013-04-07 Thread Colin J. Williams
On 07/04/2013 1:03 AM, Ondřej Čertík wrote: On Tue, Mar 26, 2013 at 6:32 PM, Ondřej Čertík wrote: [...] Yes. I created an issue here for them to test it: https://github.com/scikit-learn/scikit-learn/issues/1809 Just to make sure. Th

[Numpy-discussion] mrecarray indexing behaviour

2013-04-07 Thread Joel Nothman
Hello all! I am a bit confused by the behaviour of mrecarray: >>> import numpy.ma.mrecords >>> data = [(1, 'a'), (2, 'b')] >>> ra = numpy.rec.fromrecords(data) >>> mra = numpy.ma.mrecords.fromrecords(data) >>> ra rec.array([(1, 'a'), (2, 'b')], dtype=[('f0', '>> mra masked_records( f0 :

[Numpy-discussion] ANN: NumPy 1.7.1 release

2013-04-07 Thread Ondřej Čertík
Hi, I'm pleased to announce the availability of the final NumPy 1.7.1 release. Sources and binary installers can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.7.1/ Only three simple bugs were fixed since 1.7.1rc1 (#3166, #3179, #3187). I would like to thank everybody who cont