Re: [Jython-dev] Static usage in jython - can we have less of it?

[<Mat...@i2...>]

If your system classpath has no jython libs in it, and you setup a 
classloader to include the jython libs, then if you create each of your 
interpreters using this classloader, each interpreter will be completly 
isolated from any others because static data is only static w.r.t. the 
classloader that loads it.  Only problem you'll have is that multiple 
conscurrent interpreters could end up stepping on each others jar 
cache-dir (or any other files on disk) unless you give them different 
homes (File.createTempFile for each python.home).  Performance isn't as 
good either as each interpreter maintains a separate module cache.  Hope 
this helps,


Matt

On 02/10/2002 09:15:38 PM jython-dev-admin wrote:
> 
> The problem that I'm running into is that there appears to be quite a 
lot of 
> static data in the jythonworld.  The command line arguments are buried 
in the 
> SystemStatewhich is global. The package manager also appears to be 
global since 
> an import in a subsequent interpreter is misbehaving badly.  Is there 
standard 
> setup that I'm missing that might avoid all of these problems and keep 
the 
> state of the interpreters much mode independent?