>>Packaging, i.e. in war files or webstart, is a different issue; if
>>you're having difficulties with any of these areas, ask specific
>>questions to the list.
> I think you're missing the central thesis here Alan, which is (apologies
> for the reiteration) that Java bytecode is what most potential Jython
> developers want, not a Python interpreter with access to Java methods that
> relies on a JVM Runtime/exec instead of Python interpreter..
Few things to say
1. JVM Runtime/exec has nothing to do with it.
PythonInterpreter.exec() is what you mean, I think.
2. You keep asserting that what you want is what most developers want.
> This is not a different issue. This is _the_ issue. This is the reason
> Jruby has become the Java scripting language of choice while Jython has
In your opinion, jruby is everything, jython is nothing. You seem very
attached to that opinion, so I won't try to persuade you otherwise.
(As a datapoint, we're using cpython, jython and groovy where I work
Perhaps if you told us facts, i.e. the details of the *actual problem*
you're trying to solve, rather than opinions, we could have a
> A JVM Python source interpreter or even bytecode interpreter
> is cool to be sure, and useful in a limited number of circumstances
I've been using jython since 1999, and I've used it in all kinds of
situations; I wouldn't call that "limited circumstances". I've been a
reader of this list for all that time, and I don't think it applies to
the vast majority of usages described on this list.
> but it really doesn't offer significant benefits over standard Python.
Non-sequitur. Are you really asserting that the ability the run python
programs on the JVM, calling JVM APIs, scripting java applications,
etc, etc, etc, is not a significant benefit of jython?
> generated pure Java bytecode, on the other hand, is a killer app that has
> been promised but not delivered for close to a half decade now, as the 3
> year old Netbeans announcement and your 4 year old Tim Bray URL aptly
1. In your opinion, generating .class files is the "killer app" that
"everybody wants". In my opinion, it's not, it's a minority
2. Jython 2.1 generated .class files. Jython 2.5, to be released in
coming months, will generate .class files. Jython 2.2 can only
generate .class files in limited circumstances, i.e. where the jython
code does not contain python constructs that cannot be represented in
java, i.e. generators. If you desperately need .class files, then use
jython 2.1, or a limited subset of jython 2.2, or wait for jython 2.5.
3. It is most interesting that Tim Bray professed a love of Perl in
that post. What a pity that his language of choice collapsed under the
weight of it's own complexity, so he felt it necessary to move onto
something new, i.e. Ruby. Hopefully Perl's fate will never befall
Ruby or JRuby. But if it ever does, we'll always welcome Tim back to
jython land ;-)