[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-16 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15048 ___ ___ Python-bugs-list

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-12 Thread James Kyle
James Kyle b...@jameskyle.org added the comment: I think Ned does have some good points regarding the minimal impact a reversion would have. The most poignant point is that /Library/ on OS X is not a user controlled directory whereas ~/.local is. If ~/.local exists and has packages installed,

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread James Kyle
New submission from James Kyle b...@jameskyle.org: This behavior is present on OS X 10.7 and framework builds. In this case, the /Library/Python/version paths are included in every install. I would consider this behavior non-standard as in most manual python installs only that installations

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: This is intentional behavior, you can install packages you want to share between python installations in /Library/Python instead of the regular site-packages directory. Macports could always patch their site.py file to avoid this.

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: This was added in issue4865. (The same behavior is present in 3.2 and 3.3) -- resolution: - rejected versions: +Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread Ronald Oussoren
Changes by Ronald Oussoren ronaldousso...@mac.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15048 ___ ___

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread James Kyle
James Kyle b...@jameskyle.org added the comment: Am I missing something or were the problems delineated in issue #4865 solvable by simply sys.path.append(/Library/Python/2.7/site-packages)? What would the process be for reopening this issue for discussion? I'm not sure this is the right way

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: Python installation are already not isolated: there is a per-user site-packages directory on all platforms that is shared between all installations of a particular python release. This directory is located in a subdirectory of ~/.local

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread James Kyle
James Kyle b...@jameskyle.org added the comment: Fair enough. Thanks! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15048 ___ ___

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread Ned Deily
Ned Deily n...@acm.org added the comment: I have to admit that I'm not keen on this feature for the reasons James cited. And I think the example of the shared user site directory is not a good analogy. In that case, you, as a user, have more control over the presence and contents of the

[issue15048] Manually Installed Python Includes System Wide Paths

2012-06-11 Thread Ned Deily
Ned Deily n...@acm.org added the comment: A few more thoughts. The original impetus for this feature was Issue4865. The use case there seem to be from users of Google App Engine back when it was released using Python 2.5. It seems to me that the use of dmg installers for Python packages has