Issue471481
Created on 2001-10-15.20:53:55 by anonymous, last changed 2001-10-15.22:18:16 by pedronis.
History | |||
---|---|---|---|
Date | User | Action | Args |
2001-10-15 20:53:55 | anonymous | create |
Created on 2001-10-15.20:53:55 by anonymous, last changed 2001-10-15.22:18:16 by pedronis.
Messages | |||
---|---|---|---|
msg426 (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-10-15.20:53:55 | |
I'm working on an application that will use Jython as its embedded scripting language. We'll be calling Jython scripts from different contexts in the application and would like to run scripts using different initial states. For example, one set of scripts is allowed to instantiate certain Java packages but not others. Also, allowed supporting modules are found in different directory locations. Any plans to make systemState instance specific vs. global? Any big gotchas I should know about before I go digging in? If I fix things, would you be willing to accept patches? Thanks, Steve |
|||
msg427 (view) | Author: Samuele Pedroni (pedronis) | Date: 2001-10-15.22:18:16 | |
Logged In: YES user_id=61408 This would have been a feature request not a bug ;) but systemState can already be made instance specific with a ctr call of the form: new PythonInterpreter(null,new PySystemState()) also that specifies an explicit PySystemState instance. What is static or not in PySystemState it's another matter - that can be discussed. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2001-10-15 20:53:55 | anonymous | create |
Supported by Python Software Foundation,
Powered by Roundup