Jython and Pypy is interesting, but here are some clarifications (correct me if I'm wrong).
Writing Jython with Pypy would _not_ mean writing Jython in Jython. Here is what that woud be :
Pypy projects contains :
- A python tp <other language> translator (C, for instance)
- A python interpreter, written in python
...and the first python code that you want to translate in <other language> is the python interpreter itself.
...so you have a python interpreter (witten in python but translated to <other language>) which runs your python code.
So, you may want to create a "python 2 java " translator. That woud enable your python interpreter (written in python) to be translated in Java, then this "java" python interpreter woud be able to execute python code. (By the way, there are funny people that just try to interpret... the interpreter again... to interpret python code, life is so funny !)
But it would not be "java-integrated" as Jython is, not without a lot of work.
I personnaly think pypy is the right very long term approach, but I think the current Jython approach is the right one on the short term. The main point is that the Pypy approach enables you to have a single python code for your interpreter, whatever the targeted language (where it will be translated). Modifying the interpreter behaviour becomes much easier. And the integration with the targeted language becomes an isolated problem for each language (which does not mean it is not a BIG issue anyway).
But working on a "python 2 java" translator would be complex, not to mention the java integration !
2 cents, again,
firstname.lastname@example.org [mailto:email@example.com] De la part de Leo User
Envoyé : jeudi 30 mars 2006 17:45
Objet : [Jython-users] What are the implications of Jython going PyPy?
I just thought Id toss this out in the open since Ive
seen some talk about Jython becoming implemented like
PyPy. First off, I don't know much about PyPy but
from the sounds of it, its about implementing Python
in itself. I guess having Jython do the same thing is
to have Jython be implemented in itself. So this
comes to my big question:
What would going in that direction mean for tools
built on top of Jython.
Ive got 2 classes of apps in mind:
1. Those that just use Jython as Jython. jyleo, for
2. Those that build using the Jython classes. jyleo's
JythonShell is an example here. Its pure Java and
uses alot of Jython's Java classes to acheive its
Im surmising a goal of going PyPy would be to make #1
class apps work fine. But what are the implications
of #2? Does my valuable code suddenly become a thing
that can't jump into the future? Granted there will
probably be work between jython version to jython
version to have it work. I had to do some recoding to
get it to work from jython 2.1 to jython 2.2.
What about other Java apps that embed Jython in
themselves and do like the JythonShell does and uses
Jython's Java classes?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
Jython-users mailing list