retitle 503168 virtualenv shouldn't hard-code absolute path severity 503168 wishlist tags 503168 upstream thanks
On Thursday 23 October 2008 17.53:26 Jeff Licquia wrote: > Adrian von Bidder wrote: > > Shouldn't PYTHONPATH be set inside a virtual environment to allow easy > > installation of local modules? > > I don't think so. Wouldn't that break if the user sets PYTHONPATH > manually? > > It shouldn't be necessary, either. I just tested installing new local > modules in a virtualenv using activate, and was able to use both > easy_install and "python setup.py install". > > Were you having problems installing local modules before? My mistake. I moved the environment and didn't realise that the problem I've been having stems from having the old absolute path inside bin/activate and not from not having PYTHONPATH. So the proper solution [for me] would be to look at $0 and pwd and figure out the root dir of the virtualenv from there. (I like to be able to move/copy around the virtualenv to organize my projects.) cheres -- vbi -- featured link: Debian Bookmark Collection - http://bookmarks.debian.net/
signature.asc
Description: This is a digitally signed message part.
