RE: [Jnumerical-general] Porting issues and Jython 2.2

[brian z. <bz...@zi...>]

All,

From the README included with Numeric (I don't have Python 2.0 to confirm):

 Versions after 20.0 require Python 2.0 or later. To take advantage of
 the "rich comparisons" (i.e., to be able to compare arrays and get
 back a boolean result) you need Python 2.1.

I agree completely with your concerns about Numeric eventually requiring >
Python 2.2 but the only *big* difference between CVS jython and Python 2.2
is new style classes AFAIK.  I don't think Numeric makes use of this new
feature though it certainly could.

In any case I'm going to look through the source more thoroughly to see how
much of an effort it would require to refactor parts of JNumeric to make use
of Numeric's Python interface.  Most of multiarray is exposed in
PyMultiarray as static methods and some of the other required C modules are
implemented in part in Java as well.  I'd really like to see LinearAlgebra
implemented as a lapack_lite module rather than re-write LinearAlgebra.py.
We'll see.

Does anyone know about the upcoming migration from Numeric to Numarray?
What affect will this have JNumeric?

thanks,

brian

> -----Original Message-----
> From: jnu...@li...
> [mailto:jnu...@li...]On Behalf Of
> Daniel Lemire
> Sent: Tuesday, January 07, 2003 9:16 AM
> To: jnu...@li...;
> jnu...@li...
> Subject: [Jnumerical-general] Porting issues and Jython 2.2
>
>
> Good day,
>
> It seems to me that your way would be much better.
>
> One issue I see though is that jython is basically frozen since
> January 2001,
> 2 years ago at version 2.1, whereas Python is constantly evolving
> (they are
> at version 2.3) so that it might not be so simple. Anybody knows
> when Jython
> 2.2 will come out?
>
> The latest Numeric relies on 2.2 as far as I know. It might still
> run in 2.1,
> I don't know... but I'm not sure. For sure, it is only a matter of time
> before they require 2.2.
>
>
>
>
> > On that topic, why was it chosen to reimplement Numeric.py in Java
> > rather than just re-use the existing Python-based modules included in
> > Numeric and just making sure that the modules originally written in C
> > (multiarray for instance) are properly exposed through Java so Jython
> > can access them.  This does require a Jython user to download and
> > install Numeric but it would make for less work on JNumeric's side as
> > well as forcing API consistency (so long as all methods are implemented
> > but this problem exists even if re-written in Java) with Numeric.  I
> > chose this approach when porting mx.DateTime to Jython [4] and it made
> > for a lot less work.
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Jnumerical-general mailing list
> Jnu...@li...
> https://lists.sourceforge.net/lists/listinfo/jnumerical-general