wasm-demo/demo/ermis-f/python_m/cur/0115

44 lines
1.4 KiB
Plaintext

From: arnold at dstc.edu.au (David Arnold)
Date: Mon, 19 Apr 1999 03:17:15 GMT
Subject: Simple module installation
In-Reply-To: Your message of "Fri, 16 Apr 1999 14:53:32 +0200."
<371732CC.201012AF@lemburg.com>
References: <371732CC.201012AF@lemburg.com>
Message-ID: <199904190317.NAA12600@piglet.dstc.edu.au>
Content-Length: 1045
X-UID: 115
-->"Marc-Andre" == M -A Lemburg <mal at lemburg.com> writes:
Marc-Andre> Paul Prescod wrote:
>> The PYTHONPATH and PATH would be unneccessary if Fnorb used
>> the Windows registry.
in previous versions, Fnorb used the windows registry. however, this
has now been removed because it caused endless problems: users would
reinstall python, and all their fnorb code would break (since it used
the previous installation's paths). so then they had to reinstall
fnorb, even though nothing had changed, and then they had two fnorb
installations, and ...
so now you have a couple of environment variables, and a batch file
which sets them to the "guessed" values. when you python installation
changes, you can edit the batch file (easier and safer than editing
the registry).
>> Even so, I think that a Python-managed, portable, text file-based
>> registry (like JPython's) would be better than depending upon the
>> over-centralized Windows registry.
we're hoping that the distutil-sig will come up with a nice solution
;-)
d