What are the implications of Jython going PyPy?

howdy,

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
example.
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
integration.

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?

thanks!
leouser

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
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!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642