Vinay Sajip added the comment:
> as far as I know virtualenv does not create links for local/bin and friends
> either.
AFAIK it never used to, but it seems to do so since 1.6.3, in an attempt to fix
a problem with the "posix_local" install scheme. I just tested with virtualenv
1.6.4, and when I create a venv in /tmp/venv, it creates a symbolic link
/tmp/venv/local which points back to /tmp/venv. This behaviour causes problems
with e.g. PyCharm, which shows ever-nesting directories ("turtles all the way
down"), has led to later versions of virtualenv creating an actual directory
and symlinking the venv's contents to entries in it.
The question is: is this still necessary? Why exactly does "posix_local" need
this, and does it need it for Python 3.3, 3.4 etc? Adding Carl to nosy, hoping
he can shed some light on this.
----------
components: +2to3 (2.x to 3.x conversion tool), Benchmarks, Build, Cross-Build,
ctypes -None
nosy: +carljm
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16480>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
