setuptools and distribute don't prepend PYTHONPATH to sys.path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Tahoe-LAFS |
New
|
Unknown
|
|||
distribute |
Invalid
|
Undecided
|
Unassigned | ||
python-setuptools |
Unknown
|
Unknown
|
|||
distribute (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
python-setuptools (Ubuntu) |
Opinion
|
Undecided
|
Unassigned |
Bug Description
This is a long-standing issue in setuptools, which was copied into distribute when distribute forked. There exist patches the attempt to fix the issue offered against both setuptools and distribute. There are tickets in the setuptools issue tracker, distribute issue tracker, and the Tahoe-LAFS issue tracker (where we maintain a fork of setuptools in order to fix this among other outstanding bugs).
The crux of the problem is that the Python documentation says:
"The PYTHONPATH variable can be set to a list of paths that will be added to the beginning of sys.path."
http://
This is true with standard distutils, false with setuptools, false with distribute, and true if you apply the following patch to either setuptools or distribute:
Index: setuptools/
======
--- setuptools/
+++ setuptools/
@@ -1365,5 +1365,5 @@
" del sys.path[
- " p=getattr(
+ " p=getattr(
" sys.__egginsert = p+len(new)\n"
) % data
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in tahoe-lafs: | |
status: | Unknown → New |
Changed in python-setuptools (Ubuntu): | |
assignee: | nobody → Barry Warsaw (barry) |
Status changed to 'Confirmed' because the bug affects multiple users.