[PYTHON MATRIX-SIG] Finalized 0.3 interface (hopefully)

[Hinsen Konrad]

   This C type WILL continue to implement automatic type coercion, but I
   reserve the right to remove it if I continue to have problems making
   my floating point code work in floats instead of doubles.

But at some point it will have to be stable!

   4) Two python object UserArray.py and Matrix.py where Matrix
   inherits from UserArray.

I wonder about the meaning of "User" in the name "UserArray".  Does it
mean "the arrays that users really want"? My first idea when seeing
such a name would be "user-defined arrays", which is not at all what
we are talking about. I still propose to explore whether it is really
definitely impossible to use the name "Array", but if that is the
case, then something like "NumericArray" would make more sense than
"UserArray".

   I plan to package this up as an addition to the standard python
   distribution, therefore, installation will consist of adding files to
   Modules, Lib, and Include.  Does this strike anybody as an
   unreasonable thing to do?

It's probably the only reasonable thing to do for now. When my patches
are part of the standard distribution (i.e. in Python 1.4), it should
be possible to package everything as a standard extension.

-------------------------------------------------------------------------------
Konrad Hinsen                     | E-Mail: hinsenk@ere.umontreal.ca
Departement de chimie             | Tel.: +1-514-343-6111 ext. 3953
Universite de Montreal            | Fax:  +1-514-343-7586
C.P. 6128, succ. Centre-Ville     | Deutsch/Esperanto/English/Nederlands/
Montreal (QC) H3C 3J7             | Francais (phase experimentale)
-------------------------------------------------------------------------------

=================
MATRIX-SIG  - SIG on Matrix Math for Python

send messages to: matrix-sig@python.org
administrivia to: matrix-sig-request@python.org
=================