|
There are, as far as I can see, three different ways to help in this case and I am looking into implementing all of them very soon, definitely for the next release.
CPython uses environment variables PYTHONSTARTUP and PYTHONPATH to drive the initialization of the interpreter Also, on initialization, the interpreter executes statement “import site” which is the third way to hook into the initialization process.
As for the environment variables go, there is a question of naming. One possibility is to use the well-known names (PYTHONSTARTUP, PYTHONPATH) and another is to use our own: IRONPYTHONSTARTUP and IRONPYTHONPATH. We prefer the latter (names prefixed with IRON) to avoid conflicts for those of us who use CPython and IronPython on the same machine.
Unless there is strong reason to use the standard names, we will go forward with the IRONPYTHON… ones.
If you feel one way or another, please let us know. For the purpose of the environment variable naming, we are not considering other naming schemes so the choice is either standard names, or IRONPYTHON* ones.
Keith, I think this should provide you with the tools you need for your work, correct? We will try to get this update out even sooner than usual.
Martin
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Keith J. Farmer
Perhaps (to at least keep the .NET way) a .config file instead of an environment variable?
That file *could* specify one or more startup files, to maintain the Python mystique.
From:
[EMAIL PROTECTED] on behalf of Michael Spencer Second
feature request of the week: |
_______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
