Re: [Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Travis Oliphant
Charles R Harris wrote: > > > On 2/27/07, *Travis Oliphant* <[EMAIL PROTECTED] > > wrote: > > Charles R Harris wrote: > > > > > > The problem is that we aren't really specifying floating-point > > standards, we are specifying float, double and

Re: [Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Charles R Harris
On 2/27/07, Travis Oliphant <[EMAIL PROTECTED]> wrote: Charles R Harris wrote: > > > The problem is that we aren't really specifying floating-point > standards, we are specifying float, double and long double as whatever > the compiler understands. > > There are some platforms wh

Re: [Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Travis Oliphant
Charles R Harris wrote: > > > The problem is that we aren't really specifying floating-point > standards, we are specifying float, double and long double as whatever > the compiler understands. > > There are some platforms which don't follow the IEEE 754 standard. > This format

Re: [Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Charles R Harris
On 2/27/07, Travis Oliphant <[EMAIL PROTECTED]> wrote: Charles R Harris wrote: > > > On 2/27/07, *Travis Oliphant* <[EMAIL PROTECTED] > > wrote: > > PEP: > Title: Revising the buffer protocol > Version: $Revision: $ > Last-Modified: $Date: $ > Auth

Re: [Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Anne Archibald
On 27/02/07, Travis Oliphant <[EMAIL PROTECTED]> wrote: > The problem is that we aren't really specifying floating-point > standards, we are specifying float, double and long double as whatever > the compiler understands. > > There are some platforms which don't follow the IEEE 754 standard. > Thi

[Numpy-discussion] NumPy in Teaching

2007-02-27 Thread Steven H. Rogers
I'm doing an informal survey on the use of Array Programming Languages for teaching. If you're using NumPy in this manner I'd like to hear from you. What subject was/is taught, academic level, results, lessons learned, etc. Regards, Steve ___ Numpy

Re: [Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Travis Oliphant
Charles R Harris wrote: > > > On 2/27/07, *Travis Oliphant* <[EMAIL PROTECTED] > > wrote: > > PEP: > Title: Revising the buffer protocol > Version: $Revision: $ > Last-Modified: $Date: $ > Author: Travis Oliphant <[EMAIL PROTECTED] >

Re: [Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Charles R Harris
On 2/27/07, Travis Oliphant <[EMAIL PROTECTED]> wrote: PEP: Title: Revising the buffer protocol Version: $Revision: $ Last-Modified: $Date: $ Author: Travis Oliphant <[EMAIL PROTECTED]> Status: Draft Type: Standards Track Created: 28-Aug-2006 Python-Version: 3000 Additions to the struct

Re: [Numpy-discussion] Buffer Interface for Python 3.0

2007-02-27 Thread Anne Archibald
On 27/02/07, Travis Oliphant <[EMAIL PROTECTED]> wrote: > Basically, what we are going to do now is > > 1) Return the data-format specification in an extended struct-style string > 2) Return the shape information in a tuple of lists: (shape, strides) > > There are two questions I'm grappling with

[Numpy-discussion] Draft PEP for the new buffer interface to be in Python 3000

2007-02-27 Thread Travis Oliphant
PEP: Title: Revising the buffer protocol Version: $Revision: $ Last-Modified: $Date: $ Author: Travis Oliphant <[EMAIL PROTECTED]> Status: Draft Type: Standards Track Created: 28-Aug-2006 Python-Version: 3000 Abstract This PEP proposes re-designing the buffer API (PyBufferProcs function p

[Numpy-discussion] Buffer Interface for Python 3.0

2007-02-27 Thread Travis Oliphant
An update for those of you who did not get the chance to come to PyCon. PyCon was very well attended this year and there were some excellent discussions and presentations. From PyCon I learned that Python 3000 is closer than I had previously thought. What this means for me, is that I am now

[Numpy-discussion] [ANN] mlabrap-1.0b: a high level python to matlab

2007-02-27 Thread Alexander Schmolck
URL --- Description --- Mlabwrap-1.0 is a high-level python to matlab(tm) bridge that makes calling matlab functions from python almost as convenient as using a normal python library. It is available under a very liberal license (BSD/MIT) and should work

[Numpy-discussion] building an array using smaller ones

2007-02-27 Thread Rudolf Sykora
Hello everybody, I wonder how I could most easily accomplish the following: Say I have sth like: a = array( [1, 2] ) and I want to use this array to build another array in the following sence: b = array( [[1, 2, 3, a], [5, a, 6, 7], [0, 2-a, 3, 4]]) # this doesn't work I would like to obtain b

[Numpy-discussion] inconsistent mgrid results

2007-02-27 Thread Andrew Corrigan
I'm confused about the following: >>> print mgrid[2.45:2.6:0.05, 0:5:1] [[[ 2.45 2.45 2.45 2.45 2.45] [ 2.5 2.5 2.5 2.5 2.5 ]] [[ 0.1.2.3.4. ] [ 0.1.2.3.4. ]]] >>> print mgrid[2.45:2.6:0.05] [ 2.45 2.5 2.55] In the first case in the first dime

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-27 Thread Alexandre Fayolle
On Sun, Feb 25, 2007 at 06:44:37PM +0200, Jouni K. Seppänen wrote: > "Barry Wark" <[EMAIL PROTECTED]> writes: > > > Yes, I agree. I wasn't coming at so much from the goal of making Pylab > > a Matlab clone (as you point out, that's silly, and misses much of the > > advantage of Python), but rather