[Jnumerical-general] Porting issues and Jython 2.2

[Daniel L. <le...@on...>]

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.