Éric Araujo added the comment:
It was linked from the blog post (see first message):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695758
--
stage: - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16480
Marten Lehmann added the comment:
Which bug ID? Couldn't find it anywhere in the previous comments.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16480
___
Marten Lehmann added the comment:
Could you please tell me, in which exact release or commit this is resolved?
I'm using Python 3.3.0 on Ubuntu Precise and I noticed like the others, that
e.g. easy_install and pip are installed to venv/local/bin instead of venv/bin
and the site-packages
Éric Araujo added the comment:
From Python’s viewpoint this is closed, please follow up on the Debian bug
tracker.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16480
___
Matthias Klose added the comment:
fixed in experimental, pyvenv's are now handled the same way as
python-virtualenvs. closing the issue here.
--
resolution: - works for me
status: open - closed
___
Python tracker rep...@bugs.python.org
Matthias Klose added the comment:
having the posix_prefix as the default in Debian is an oversight on my side. it
always should be posix_local. I'll fix this at least for 3.3 in current
development releases.
The rationale for this is that distutils based installs install by default into
the
Vinay Sajip added the comment:
Even when posix_local becomes the default scheme on Debian python builds,
it's not clear whether the suggested fix is the correct one to make, unless
posix_local is added to sysconfig's list of _INSTALL_SCHEMES. Matthias
comment makes sense when considering
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16480
___
___
Python-bugs-list mailing
Matthias Klose added the comment:
virtualenv for 2.7, when used with a Debian/Ubuntu system installation, should
only see site-packages. Same thing should be done for venv for 3.3 and up.
Even if needed patches will not go upstream, they are welcome.
--
Changes by Matthias Klose d...@debian.org:
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16480
___
___
Python-bugs-list mailing
Vinay Sajip added the comment:
IIUC, Debian Experimental is not a complete distribution. Are there other,
non-experimental OS variants where posix_local is used with Python 3.x?
On my Ubuntu Oneiric and Precise 64-bit machines, the default install scheme on
the official Python 3.2 - as
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
Carl Meyer added the comment:
What OS are you on, Marco?
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.
--
___
Python tracker
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
Éric Araujo added the comment:
Is it impossible to edit the install scheme when run in a venv, so that the
workaround becomes unnecessary? We are the upstream after all :)
--
versions: +Python 3.4
___
Python tracker 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.
That's
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
Changes by Andrew Svetlov andrew.svet...@gmail.com:
--
nosy: +asvetlov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16480
___
___
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
Vinay Sajip added the comment:
Whoops, mouse glitch led to components being wrongly set.
--
components: +Library (Lib) -2to3 (2.x to 3.x conversion tool), Benchmarks,
Build, Cross-Build, ctypes
___
Python tracker rep...@bugs.python.org
Ned Deily added the comment:
What problem are you trying to solve here? pyvenv is working as documented.
And, although pyvenv does not claim to be compatible with the third-party
virtualenv package, as far as I know virtualenv does not create links for
local/bin and friends either.
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16480
___
___
Python-bugs-list
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
23 matches
Mail list logo
