➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: PackMan needs to be able to install outside site-packages
Type: Stage:
Components: macOS Versions:
process
Status: closed Resolution: works for me
Dependencies: Superseder:
Assigned To: jackjansen Nosy List: jackjansen
Priority: low Keywords:

Created on 2003-06-27 22:26 by jackjansen, last changed 2022-04-10 16:09 by admin. This issue is now closed.

Messages (2)
msg16637 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-06-27 22:26 
PackMan needs to be able to install system-wide packages 
in /Library/Python/2.3/site-packages, in the event that the 
normal $prefix/lib/python2.3/site-packages is not writeable. 
That directory also needs to be put on sys.path (for 
framework OSX builds only) if it exists, similarly to ~/
Library/Python/2.3/site-packages.
msg16638 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-06-28 23:28 
Logged In: YES 
user_id=45365

It turns out this is less of a problem than I feared: site-packages 
is a symlink to a place that is writable. There is still a problem 
when a distutils-based package tries to install extra header files, 
but that will have to be solved after 2.3b2.
History
Date User Action Args
2022-04-10 16:09:29adminsetgithub: 38727
2003-06-27 22:26:49jackjansencreate