New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
virtualenv --always-copy fails on CentOS (lib64 problem?) #1332
Comments
Hi, an info for future users, in case they need a fix before this bug is smashed. Since my project is on python3, I sidestepped the poblem replacing:
with
This works on CentOS 7.x (no |
So the option name has changed? |
Hi @tobiasherp, not exactly. The two options refer to different programs: What I did is ditching virtualenv altogether, and use |
I see
When i attempt to run |
I'm seeing the same issue on OpenSUSE 15.0 and 15.1.
@gaborbernat Any ideas here? Without |
I tried the
|
@archon810, that's true: I do not know if it's enough for your needs. For me the use case was making sure that a user did not inadvertently mess up file permission in other directories while operating on his virtualenv. In this case it s acceptable that /lib64 is a symlink, since it stays within the virtualenv directory structure. Side note: with python3 having available |
I'm trying to set up a Python env inside WSL on Windows, in a Dropbox folder, and Dropbox gets confused by any symlinks. This is the last set of symlinks left for me to figure out, and virtualenv was pretty much there, had it not had this math crash. I mean, I could add an rm and cp -R to venv and try to go that route, but it'd be good if it actually did what it says it's doing and didn't have symlinks at all.
|
Ughhh, turns out virtualenv pip has this and works:
venv pip has this and outputs an error:
|
Confirmed this |
This is a ugly bug you found. From its looks, seems a missing quoting in some bash script (which would not surprise me, given how often this is overlooked). I'll try to find it, since this kind of stuff scratch an itch for me. It won't solve your problem, but at least we'll get out with something good for someone. |
#1500 should solve this now once and for all. |
Creating a virtualenv with
--always-copy
on a platform that uses/lib64
directory seems to be impossible.On CentOS 7.6, the same happens both with the system packages (python 2.7.5, virtualenv 15.1.0) and the ones installed via SCL.
There are some tickets that may be related (#985, #1192, #3477, FPGAwars/icestudio#244), and a merged pull request that supposedly fixes the problem (#1189), yet I have the impression that there is still something wrong happening.
Example using SCL (Python 3.6.3, virtualenv manually upgraded to 16.4.3).
The first error seems to happen in
virtualenv_support/pip-19.0.3-py2.py3-none-any.whl
:Complete log to see it in context.
I have really tried lots of combinations (many versions, playing with PATH and PYTHONPATH) with no luck. Any help appreciated.
The text was updated successfully, but these errors were encountered: