[Numpy-discussion] Uncomfortable with matrix change

Keith Goodman kwgoodman@gmail....
Sat May 10 16:50:47 CDT 2008


On Sat, May 10, 2008 at 2:35 PM, Timothy Hochberg <tim.hochberg@ieee.org> wrote:
> Please, let's just leave the current matrix class alone. Any change
> sufficient to make matrix not terrible, will break everyone's code. Instead,
> the goal should be build a new matrix class (say newmatrix) where we can
> start from scratch. We can build it and keep it alpha for a while so we can
> break the interface as needed while we get experience with it and then,
> maybe, transition matrix to oldmatrx and newmatrix to matrix over a couple
> of releases. Or just choose a reasonable name for matrix to begin with
> (ndmatrix?) and then deprecate the current matrix class when the new one is
> fully baked.
>
> Trying to slowly morph matrix into something usable is just going to break
> code again and again and just be a giant headache in general.

+1

That sounds ideal to me. What's the first step? A design spec on the wiki?


More information about the Numpy-discussion mailing list