From: Moore, G. <Gre...@ad...> - 2008-07-31 19:40:15
|
Hi Nicholas, For my 2 cents worth, I like your suggestions and think they will help clarify things going forward. I'm wondering if having something like, for example, 'JythonImports' setting the that could be used to specify where external libraries are so they can be found when using standalone Jython or in a web application environment. Something kinda like a classpath but could also include python modules as well as java. This might make it easier to have multiple instances of Jython each with a unique environment as needed by the web app. However, I'm not sure if this is doable or what sort of coding it would require. One other comment instead of just calling it simply 'registry' would clearer to call it Jython.registry or maybe Jython.settings or even something like in the java world... Jython.properties Thanks for your time. Greg. -----Original Message----- From: jyt...@li... [mailto:jyt...@li...] On Behalf Of Nicholas Riley Sent: Thursday, July 31, 2008 12:02 PM To: jyt...@li... Cc: jyt...@li... Subject: [Jython-dev] Jython settings - input requested Hi folks, We're trying to clean up the multitude of ways Jython reads settings (properties, options) and would appreciate your input on what bits of customization you use and which ones you'd like to see added or removed. Jython reads settings/options/properties at startup from several sources. From the standpoint of a user of the interactive interpreter, they are: - Java system properties (-J-Dxxx=yyy with new launcher script) - Registry (prop=value in file jython_home/registry or $HOME/.jython) - Jython properties (-Dxxx=yyy) There exist several partial attempts at documenting these settings. I've attempted to enumerate them all here: <http://wiki.python.org/jython/Settings> Some cases in which I'm pretty sure Jython is not behaving as designed or expected: 1. If a registry file is present, the Java system properties are ignored completely. 2. If both registry files are present, the "registry" one is ignored completely. 3. If a property exists in the registry, it takes precedence over a command-line option (e.g., python.verbose trumps -v[vv]). Some changes I'm considering making: 1. Merge system properties and registry files into the registry, rather than replacing them outright. 2. Make command-line options take precedence over registry options. 3. Read from the JYTHONPATH environment variable, replacing python.path in the registry (or in system properties?). This is analogous to IronPython's IRONPYTHONPATH. CPython understands a bunch more environment variables (e.g. PYTHONDEBUG, PYTHONINSPECT) but I'm not sure we really need to support them, either in place or renamed. Should the JYTHONPATH mapping happen in the launcher scripts or Jython itself? One last thing: in CPython, setting PYTHONPATH places the items after the current directory, but before the standard library. Setting python.path in Jython places the items after the standard library; you must use python.prepath to get the CPython behavior. It looks like the reason for this change is no longer applicable: <http://www.jython.org/cgi-bin/faqw.py?req=show&file=faq02.003.htp> as the Python standard library is now included with Jython by default, so perhaps python.prepath should be removed and python.path take its place? Or do we need a python.postpath? Does anyone take advantage of this ordering? -- Nicholas Riley <nj...@ui...> ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Jython-dev mailing list Jyt...@li... https://lists.sourceforge.net/lists/listinfo/jython-dev This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. |