No Support for --home=~ Python Installations

[trac@…]

Set severity as major as this pretty much completely prevents the use of trac on a system in which —home=~ is used. I initially patched the setup.py to change the siteconfig method in my_install (attached), however there are more problems, the search path gets messed up as well causing the scan for plugins to attempt to create (via setuptools) /Library/Webserver/.python-eggs

[trac@…]

patch for setup.py

[Emmanuel Blot]

I may not understand the bug report, but ~home should be used with care: ~home should be replaced with $HOME, as the shell (which translates the ~home alias into the actual directory) may not work when ~ is prefixed with other characters, such as —install-dir= for example.

Can you give more details about the actual issue ?

[trac@…]

Digging into this a little more, the second problem seems to be somewhat related to the setuptools side of things, due to being in a CGI script setuptools tries to use the cwd as the place to unpack the eggs but since it is not writable by the script (the web server runs it as nobody) it can't make the directory… and that is covered in the PYTHON_EGG_CACHE bit in the CGI install… so just the first problem please ;)

Re: your response

there is no "~home" that is a shell magic folders thing, i am talking about using a —home=~ set up in python: ​http://python.org/doc/current/inst/alt-install-windows.html#SECTION000310000000000000000

[Christopher Lenz]

This is a duplicate of #963.