This is a look into the distant future, but it looks like it will definitely
be an advantage to use Java 5 for anything beyond a 2.4 adaptation. Python
3.0 will have function annotations: http://oakwinter.com/code/?p=36 ...some
of the Java 5 capabilities could make this transition smoother.
> I could be persuaded to move up the future min environments some.
> Maybe something like this:
> Jython 2.2: Java 1.2
> Jython 2.3: Java 1.4
> Jython 2.4: ? Depends on how quickly we get to it, but either Java
> 1.4 or Java 5.
> I think there are some things that would go more quickly, and it
> certainly would be easier to feel confident about the testing.
> I'm leaving Jython 2.2 at the Java 1.2 level just because it was
> already developed with that constraint, and I see no reason to throw
> that away.
> Note that I do intend to get 2.3 out pretty quickly after 2.2 (I hope
> it is no more than a 6 month lag). This is because 2.2 is already
> based more on CPython 2.3 than it is based on CPython 2.2, so it
> really shouldn't take that long. The one big difference is that the
> Java Dispatch algorithm needs to take PyBoolean into account for 2.3,
> and I don't want to take the time to do that for the 2.2 release.
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> Jython-dev mailing list
From: Frank Wierzbicki <fwierzbicki@gm...> - 2006-07-11 14:36:44
On 7/11/06, j.juneau@... <j.juneau@...> wrote:
> This is a look into the distant future, but it looks like it will definitely
> be an advantage to use Java 5 for anything beyond a 2.4 adaptation. Python
> 3.0 will have function annotations: http://oakwinter.com/code/?p=36 ...some
> of the Java 5 capabilities could make this transition smoother.
There is no question (at least to me) that we will use the latest and
greatest for any 3.0 work. I would say we might even use whatever
Java is in *beta* when we start the 3.0 (or 3000 if you prefer)
planning. Since Python 3.0 and therefore Jython 3.0 are to be
intentionally backwards incompatible, we will have much more latitude
with this sort of thing. Also, the adoption of Python/Jython 3000
would be expected to be pretty gradual, since re-work will be
necessary in most cases.
> - Josh