On 19.09.2006, at 20:42, Travis Oliphant wrote:
> Well, I got both ScientificPython and MMTK to compile and import
> using
> the steps outlined on http://www.scipy.org/Porting_to_NumPy in
> about 1
> hour (including time to fix alter_code1 to make the process even
> easier).
Could you ple
On 19.09.2006, at 18:48, Christopher Barker wrote:
> Konrad Hinsen wrote:
>> MMTK works fine with Numeric 23.x (and probably many other versions),
>> so I don't see a pressing need to change to NumPy.
>
> Pressing is in the eye of the beholder.
Obviously. It also depends on the context in which o
Konrad Hinsen wrote:
> On Sep 19, 2006, at 5:11, Dr. Seth Olsen wrote:
>
>
>> Bill's answer to my inquiry about the problem I'm having with
>> Collection.findTransformation() (and also, incidentally, with the
>> dgesvd call in Subspace.getBasis(), has convinced me that I can no
>> long use
Konrad Hinsen wrote:
> MMTK works fine with Numeric 23.x (and probably many other versions),
> so I don't see a pressing need to change to NumPy.
Pressing is in the eye of the beholder.
However: I don't think we should underestimate the negative impact of
the Numeric/numarray split on the usab
On Sep 19, 2006, at 5:11, Dr. Seth Olsen wrote:
> Bill's answer to my inquiry about the problem I'm having with
> Collection.findTransformation() (and also, incidentally, with the
> dgesvd call in Subspace.getBasis(), has convinced me that I can no
> long use MMTK without changing some of th
