Re: [Numpy-discussion] Things to address for Py3K

2006-10-12 Thread Rob Hetland
On Oct 11, 2006, at 1:41 PM, Travis Oliphant wrote: >a) an extra multiplication operator to distinguish between > element-by-element and dot One of the things I like about numpy is that element-by-element multiplication is default. Really, most of what I do is element by element, punctu

Re: [Numpy-discussion] Things to address for Py3K

2006-10-11 Thread Eric Firing
Charles R Harris wrote: [...] >b) extending 'and' and 'or' to allow element-by-element logical > operations or adding && and || > > 2) Lowering the precedence of & so that a > 8 & a < 10 works as you > would expect. > > > Yes on the extra operators. No on changing the preced

Re: [Numpy-discussion] Things to address for Py3K

2006-10-11 Thread Christopher Barker
A. M. Archibald wrote: > IEEE floats in python proper +1 -CHB -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main

Re: [Numpy-discussion] Things to address for Py3K

2006-10-11 Thread A. M. Archibald
On 11/10/06, Charles R Harris <[EMAIL PROTECTED]> wrote: > Speaking long term, what about data types? The basic 80 bit extended > precision float now occurs in 80, 96, and 128 bit versions depending on > alignment. So what happens when quad precision, which will probably be in > the next IEEE stan

Re: [Numpy-discussion] Things to address for Py3K

2006-10-11 Thread Christopher Barker
Travis Oliphant wrote: >> 3) Inclusion of an nd-array type in the standard lib! >> (or at the very least, an nd-array protocol) >> > Work on an nd-array protocol to extend the buffer protocol is occurring > right now. It think this will be better in the end then a standard > nd-array type. Wel

Re: [Numpy-discussion] Things to address for Py3K

2006-10-11 Thread Charles R Harris
On 10/11/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: Hi all,Py3K is undergoing active development.  This gives us an opportunity todiscuss more significant changes to the language that might improve theexperience of NumPy users.We should form a list and start commenting on the py3k mailing lists

Re: [Numpy-discussion] Things to address for Py3K

2006-10-11 Thread Travis Oliphant
Christopher Barker wrote: >Travis Oliphant wrote: > > >>A couple on my short list >> >>1) Adding a *few* new infix operators. >> >> a) an extra multiplication operator to distinguish between >>element-by-element and dot >> b) extending 'and' and 'or' to allow element-by-element logical >>o

Re: [Numpy-discussion] Things to address for Py3K

2006-10-11 Thread Christopher Barker
Travis Oliphant wrote: > A couple on my short list > > 1) Adding a *few* new infix operators. > >a) an extra multiplication operator to distinguish between > element-by-element and dot >b) extending 'and' and 'or' to allow element-by-element logical > operations or adding && and || > >