>From: =?iso-8859-1?q?Morten=20Christensen?= <mortench2003@...>
> Python is a great Programming Language & Jython
>is truly cool! So cool in fact, that I wish I could use Jython (a lot) instead of pure Java.
I agree, and in fact, I do use Jython instead of
Java-written-in-Java-syntax on a daily basis.
>Unfortunately the development status/uncertainty of Jython is too problematic for me (in order of significance):
>1) Bugs are not being fixed. I actually did report one bug and suggested
>one fix recently myself, but lost heart after finding out that other
>bugs 1-2 years back have still not been fixed.
Was this the popen issue? I looked at it, and the proposed fix was
insufficient (declaring binary mode at all times, IIRC). I intended to
work on it and get back to you, I haven't been able to get back to it -
too busy w/ doing other work... Sorry, I should have at least mentioned
I looked at it.
>2) Not clear how many - if any - are actually developing the next version and to what degree. It is also not clear if this project is now a low-priority
>hobby project or a mission-critical, strongly backed project (for me, lack of focus on fixing existing bugs suggest the first).
Samuele is the primary developer working on adding Python 2.2 features.
Personally, I've had little need of 2.2/3 features, and the "it would be
nice" has not given it enough priority to contend with all the other
things I need to do.
>3) No public plans for new versions. There is a july 2.2a0 version but nothing that yet convince me that the 2.2 is firmly on track.
>P.S. Please be aware that the intention of this message is to
>promote healthy/productive debate and to clear up the status of Jython. I wish only be best for the Jython project and deeply respect the effort
>of the Jython developers. Please read my posting in that light. Also, do not hesitate to prove me wrong. Indeed I would love it if someone do!
I'd love to be able to say, "No, we've got legions of programmers
working full-time on resolving issues and adding features to Jython",
but sadly it isn't the case. As always, volunteers are welcome.
Meanwhile, Samuele has been making progress.
Volunteers could do well in some of the following areas:
- javac - has received very little attention
- installer - probably needs to be replaced. When I did the 2.2a0
release, I was unable to get a functional build of it.
- build/test - should be easy to build a "release". Should be easy to
validate which Python std modules function correctly with Jython.
- fixing bugs
- CPython features - there are many more people working on CPython than
on Jython. Hard to keep up with that many, though they do have to work
in C... ;-)
Meanwhile, Jython's current implementation is functional, robust, and
stable enough to do _many_ things very well. To the many programmers
coming from Java, the productivity increase of the Jython 2.1 (or 2.2a0)
feature set is incredible. To programmers coming from the Python world,
the lack of 2.2/2.3 features is relatively insignificant compared with
the access to all the Java libraries.
In my opinion, while it would be great to see more rapid progress in
Jython development, Jython is and would remain a fantastic tool even if
it never added another Python feature.