[issue16480] pyvenv 3.3 fails to create symlinks for virtualenv/local/{bin, lib} to virtualenv/{bin, lib}
Marco Amadori added the comment:
2012/11/21 Carl Meyer rep...@bugs.python.org
Carl Meyer added the comment:
Here is the bug filed against virtualenv that led to the addition of the
local/ directory: https://github.com/pypa/virtualenv/issues/118
As Vinay pointed out, the original fix was later modified to be friendlier
to tools that dislike recursive symlinks.
I didn't used virtualenv but pyvenv-3.3, so if this is not a bug, my
question become:
how to proper install distribute and pip in python 3.3 venv since they
installs in VENV/local/bin and that VENV/bin/activate does not
include VENV/local/bin in $PATH ?
--
title: pyvenv 3.3 fails to create symlinks for virtualenv/local/{bin,lib} to
virtualenv/{bin,lib} - pyvenv 3.3 fails to create symlinks for
virtualenv/local/{bin, lib} to virtualenv/{bin, lib}
___
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
[issue16480] pyvenv 3.3 fails to create symlinks for virtualenv/local/{bin, lib} to virtualenv/{bin, lib}
Marco Amadori added the comment: On Wednesday 21 November 2012 21:32:57 Carl Meyer wrote: Carl Meyer added the comment: What OS are you on, Marco? Linux. Debian GNU/Linux amd64 sid/experimental. It looks to me like pyvenv probably does need the same hack as virtualenv here, to deal with OSes who set posix_local as the default installation scheme. nice! -- ___ 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
[issue16480] pyvenv 3.3 fails to create symlinks for virtualenv/local/{bin, lib} to virtualenv/{bin, lib}
Marco Amadori added the comment: 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. I hope to see the light on that too. ;-) Meanwhile, my problem was that after creating the virtualenv, as cited in the blog post above linked, I got stuck in installing pip (and thus distribute) in that virtualenv, because 'VENV/local/bin' is not in the $PATH (and it seems reasonable for a virtualenv that this will remain stable). So, (IMHO) if changing the $PATH is not a good idea, either python should do: 1. patch distribute and pip to do not install in ./local by default if in a VENV. (enviroment variable based?, whatever) 2. create the links after creating the VENV (my naïve solution) Am I right or I completely hit the wrong issue? -- ___ 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
[issue16480] pyvenv 3.3 fails to create symlinks for virtualenv/local/{bin, lib} to virtualenv/{bin, lib}
New submission from Marco Amadori:
The solution to work around the bug is there:
http://ipoveraviancarriers.blogspot.it/2012/11/python-33-and-pyvenv-hackish-solution.html
But probably pyvenv should be patched in order to create symlinks.
Thanks!
--
components: None
messages: 175626
nosy: Marco.Amadori
priority: normal
severity: normal
status: open
title: pyvenv 3.3 fails to create symlinks for virtualenv/local/{bin,lib} to
virtualenv/{bin,lib}
type: behavior
versions: Python 3.3
___
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
