Things to address for Py3K

A. M. Archibald peridot.faceted at gmail.com
Wed Oct 11 16:37:42 CDT 2006


On 11/10/06, Charles R Harris <charlesr.harris at gmail.com> 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 standard, comes down the pike and is 128 bits long? The length
> of a float will no longer be sufficient to distinguish the various types.

This doesn't require python 3K; it can happn in numpy with no language
support. But perhaps python 3K can be viewed as a chance to ditch
backwards-compatibility baggage? (cough, Numeric compatibility, cough)

Would it be of interest to have numeric datatypes integrated with
python datatypes? How about IEEE floats in python proper, at least? It
can be rather confusing when doing a calculation yields different
results for arrays than for ordinary scalars...

A. M. Archibald

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642




More information about the Numpy-discussion mailing list