From: Charlie G. <cha...@gm...> - 2007-04-26 05:41:31
|
On 4/25/07, Kevin Menard <km...@se...> wrote: > On Wed, 25 Apr 2007 16:21:42 -0400, Charlie Groves > <cha...@gm...> wrote: > > > What do you mean by a local Jython installation? As long as the > > jython classes are present, you can start up a PythonInterpreter and > > run Python code. The classes can be from a full jython install, > > jython.jar on your classpath, or by moving the jython classes into > > your jar. The only restrictions are that the classes are there and > > the security manager doesn't restrict byte code loading. > > This sounds to me like every application would require some amount of > scaffolding code to get going. I want to use Jython as non-invasively as > possible. Such scaffolding is a barrier to entry. > > With what I have now, I can simply type "mvn package", and what I get is a > single JAR containing the Jython distribution plus my .py compiled as > .class. The JAR manifest lists the compiled Jython file as the main class > and there's no additional code necessary. Ahh, I misunderstood what you were trying to do. I can't think of any way to do that with the builtin code. You need something to setup a PythonInterpreter and to tell it what file to run. That code would be really simple though, so you could generate that source as part of your maven plugin. To remove the need to set things up like that, we could add a main method to the class files we make for .py files. That could handle making an interpreter and then telling it what to execute. I'll see if we can do something like that. Charlie |