[Python-bugs-list] [ python-Bugs-798876 ] windows sys.path contains
nonexistant directory
SourceForge.net
noreply at sourceforge.net
Mon Sep 15 22:01:51 EDT 2003
Bugs item #798876, was opened at 2003-09-01 20:31
Message generated for change (Comment added) made by logistix
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=798876&group_id=5470
Category: Python Interpreter Core
Group: Python 2.3
Status: Open
Resolution: None
Priority: 4
Submitted By: logistix (logistix)
Assigned to: Nobody/Anonymous (nobody)
Summary: windows sys.path contains nonexistant directory
Initial Comment:
Starting in python 2.3, sys.path on Windows contains
the nonexistant directory "c:\python23\lib\plat-win".
I don't know if this is really a bug, since we can no
longer assume that an entry in sys.path exists or is a
physical directory. Still, it seems like each entry in
sys.path should be able to resolve to SOMETHING.
I would've flagged this low priority if I had the capability.
----------------------------------------------------------------------
>Comment By: logistix (logistix)
Date: 2003-09-15 21:01
Message:
Logged In: YES
user_id=699438
Disregard last comment. I ran a clean and the problem
disappeared.
----------------------------------------------------------------------
Comment By: logistix (logistix)
Date: 2003-09-15 20:01
Message:
Logged In: YES
user_id=699438
There's a wierd bug on line 255 of getpathp.c. The malloc
fails when trying to allocate 42 bytes, which is the length
of "\Software\Python\PythonCore\X.X\PythonPath" and it
causes the function to abort.
Just on a hunch, I bumped the malloc size up to 44 since
that's an even number of dwords, and the malloc magically
succeeded.
Also, Since I'm running XP, shouldn't the
sizeof "\Software\Python\PythonCore\X.X\PythonPath" be 84?
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2003-09-01 20:40
Message:
Logged In: YES
user_id=31435
Strange. I see it under Python 2.1.3 too. So it's not a new
thing, but somehow 2.2.3 managed to get rid of it temporarily
<wink>. Boosting the priority to 4, since it's at least a
mystery!
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=798876&group_id=5470
More information about the Python-bugs-list
mailing list