Skip to content
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

creating a virtual environment on a filesystem without symlink-support fails even with --copies #2786

Open
c33s opened this issue Oct 21, 2024 · 0 comments
Labels

Comments

@c33s
Copy link

c33s commented Oct 21, 2024

Issue

i am new to python venv, so please forgive me if i open the issue on a wrong place or missunderstood something.

as i am on a virtualmachine which is hosted on a windows system where i share the repository i am working in with the hsot system i

Environment

Provide at least:

  • OS: alpine 3.19
  • pip list of the host python where virtualenv is installed:
 pip list
Package                   Version
------------------------- --------
altgraph                  0.17.3
ansible                   8.6.1
ansible-compat            3.0.2
ansible-core              2.16.1
argcomplete               3.1.1
arrow                     1.2.3
attrs                     23.1.0
bcrypt                    4.1.1
binaryornot               0.4.4
certifi                   2023.5.7
cffi                      1.16.0
chardet                   5.1.0
charset-normalizer        3.1.0
click                     8.1.3
click-help-colors         0.9.1
cookiecutter              2.1.1
cryptography              41.0.7
distlib                   0.3.7
distro                    1.8.0
docker                    6.1.2
enrich                    1.2.7
filelock                  3.12.4
hcloud                    2.2.1
idna                      3.4
iniconfig                 1.1.1
Jinja2                    3.1.4
jinja2-time               0.2.0
jmespath                  1.0.1
jsonschema                4.17.3
markdown-it-py            2.2.0
MarkupSafe                2.1.3
mdurl                     0.1.2
molecule                  5.0.1
molecule-docker           2.1.0
molecule-podman           2.0.3
mypy                      1.6.1
mypy-extensions           1.0.0
netaddr                   0.9.0
packaging                 23.2
paramiko                  3.4.0
pip                       23.3.1
platformdirs              4.0.0
pluggy                    1.0.0
py                        1.11.0
pycparser                 2.21
Pygments                  2.15.1
pyinstaller               5.11.0
pyinstaller-hooks-contrib 2023.3
PyNaCl                    1.5.0
pyparsing                 3.1.1
pyroute2                  0.7.9
pyrsistent                0.19.3
pytest                    7.4.3
pytest-html               3.2.0
pytest-metadata           3.0.0
pytest-molecule           2.0.0
pytest-testinfra          8.1.0
python-dateutil           2.8.2
python-slugify            8.0.1
PyYAML                    6.0.1
redis                     4.5.5
requests                  2.30.0
resolvelib                1.0.1
rich                      13.3.5
ruamel.yaml               0.17.26
ruamel.yaml.clib          0.2.7
selinux                   0.3.0
setuptools                70.3.0
six                       1.16.0
subprocess-tee            0.4.1
takeltest                 0.8.0
text-unidecode            1.3
typing_extensions         4.8.0
urllib3                   2.0.2
virtualenv                20.24.6
websocket-client          1.5.1

Output of the virtual environment creation

python -m venv venv2--copies
Error: [Errno 1] Operation not permitted: 'lib' -> '/ansible/venv/lib64'

Make sure to run the creation with -vvv --with-traceback:

python -m venv venv -vvv --with-traceback
usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear] [--upgrade] [--without-pip]
            [--prompt PROMPT] [--upgrade-deps]
            ENV_DIR [ENV_DIR ...]
venv: error: unrecognized arguments: -vvv --with-traceback

my workaround is to manually specify a path an the system where symlinking is possible

maybe related to #2578

@c33s c33s added the bug label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant