Opened 10 years ago

Closed 9 years ago

#232 closed defect (invalid)

Python's path (sys.path / PYTHON_PATH) doesn't really do something sensible

Reported by: ezyang Owned by:
Priority: normal Milestone:
Component: web Keywords:
Cc:

Description

See RT 1524793, in which a user was confused about a Python path with the wrong precedence: user paths should always be the most important.

See also #10

Change History (2)

comment:1 Changed 10 years ago by andersk

Is there anything actually wrong here that isn’t just user confusion? This works for me:

[andersk@pancake-bunny]:~$ python -c 'import django; print django.VERSION'
(1, 2, 5, 'final', 0)
[andersk@pancake-bunny]:~$ easy_install --user -Z --upgrade Django
…
[andersk@pancake-bunny]:~$ python -c 'import django; print django.VERSION'
(1, 3, 1, 'final', 0)

comment:2 Changed 9 years ago by adehnert

  • Resolution set to invalid
  • Status changed from new to closed

At a glance, it looks like part of the problem might be that they were using ~/lib/, not the more pythonic(?) ~/.local/lib/.

Behavior I'm seeing with sys.path seems like what I expect, and I haven't heard more reports of this, so I'm going to resolve this as INVALID.

Note: See TracTickets for help on using tickets.