Tim Peters wrote:
I believe I documented it many moons ago. I don't think CurrentVersion was
ever implemented (or possibly was for a very short time before being
removed). The registered modules concept was misguided and AFAIK is not
used by anyone - IMO it should be deprecated (if not just
Fred L. Drake, Jr. wrote:
On Monday 10 October 2005 18:42, Tim Peters wrote:
never before this year -- maybe sys.path _used_ to contain the current
directory on Linux?).
It's been a long time since this was the case on Unix of any variety; I
*think* this changed to the current state
[Tim Peters]
never before this year -- maybe sys.path _used_ to contain the current
directory on Linux?).
[Fred L. Drake, Jr.]
It's been a long time since this was the case on Unix of any variety; I
*think* this changed to the current state back before 2.0.
[Martin v. Löwis]
Please check
On 10/11/05, Tim Peters [EMAIL PROTECTED] wrote:
Well, that's in interactive mode, and I see sys.path[0] == on both
Windows and Linux then. I don't see in sys.path on either box in
batch mode, although I do see the absolutized path to the current
directory in sys.path in batch mode on
[Tim]
Well, that's in interactive mode, and I see sys.path[0] == on both
Windows and Linux then. I don't see in sys.path on either box in
batch mode, although I do see the absolutized path to the current
directory in sys.path in batch mode on Windows but not on Linux -- but
Mark Hammond
On 10/11/05, Tim Peters [EMAIL PROTECTED] wrote:
[Tim]
Well, that's in interactive mode, and I see sys.path[0] == on both
Windows and Linux then. I don't see in sys.path on either box in
batch mode, although I do see the absolutized path to the current
directory in sys.path in batch
[Guido]
I tried your experiment but added 'print sys.argv[0]' and didn't see
that. sys.argv[0] is the path to the script.
My mistake! You're right, sys.argv[0] is the path to the script for me too.
[Tim]
The directory of the script being run was
nevertheless in sys.path[0] on both Windows
[Martin v. Löwis]
What happened to the CurrentVersion registry entry documented at
http://www.python.org/windows/python/registry.html
AFAICT, even the python15.wse file did not fill a value in this
entry (perhaps I'm misinterpreting the wse file, though).
So was this ever used? Why is it
Suppose we run script.py while playground/ is the current directory.
I'm using 2.4.2 here, but doubt it matters much. No Python-related
envars are set.
Windows (and the PIL and pywin32 extensions are installed here):
C:\playground\python24\python.exe someother\script.py
On Monday 10 October 2005 18:42, Tim Peters wrote:
never before this year -- maybe sys.path _used_ to contain the current
directory on Linux?).
It's been a long time since this was the case on Unix of any variety; I
*think* this changed to the current state back before 2.0.
-Fred
--
What happened to the CurrentVersion registry entry documented at
http://www.python.org/windows/python/registry.html
AFAICT, even the python15.wse file did not fill a value in this
entry (perhaps I'm misinterpreting the wse file, though).
So was this ever used? Why is it documented, and who
What happened to the CurrentVersion registry entry documented at
http://www.python.org/windows/python/registry.html
AFAICT, even the python15.wse file did not fill a value in this
entry (perhaps I'm misinterpreting the wse file, though).
So was this ever used? Why is it documented, and who
12 matches
Mail list logo
