[Python]Fail to create virtualenv

Question

I was trying to create a virtualenv on my vagrant centos7 with python3 and the following happens. Is there anything I can do with it? The version of virtualenv is 13.1.2 and python is 3.5.1. Thanks.

$ virtualenv -p python3 venv
Running virtualenv with interpreter /usr/local/bin/python3
Using base prefix '/usr/local'
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/site-packages/virtualenv.py", line 2363, in <module>
    main()
  File "/usr/local/lib/python3.5/site-packages/virtualenv.py", line 832, in main
    symlink=options.symlink)
  File "/usr/local/lib/python3.5/site-packages/virtualenv.py", line 994, in create_environment
    site_packages=site_packages, clear=clear, symlink=symlink))
  File "/usr/local/lib/python3.5/site-packages/virtualenv.py", line 1192, in install_python
    copy_required_modules(home_dir, symlink)
  File "/usr/local/lib/python3.5/site-packages/virtualenv.py", line 1131, in copy_required_modules
    copyfile(filename, dst_filename, symlink)
  File "/usr/local/lib/python3.5/site-packages/virtualenv.py", line 468, in copyfile
    os.makedirs(os.path.dirname(dest))
  File "/usr/local/lib/python3.5/os.py", line 241, in makedirs
    mkdir(name, mode)
FileExistsError: [Errno 17] File exists: 'venv/lib/python3.5/lib-dynload'

It looks like you already have a (possibly broken) virtualenv venv in that directory, and virtualenv doesn't overwrite existing files by default. Try removing it (rm -rf venv) and running the creation command again, or using the --clear switch for virtualenv. — user1248490
– user1248490, Commented Dec 29, 2015 at 15:14
I tried to delete and create the venv a few times and it is still not working even with the --clear. Is there any way to fix the broken virtualenv? I tried to reinstall it with pip but not working too. Or I should just reinstall the whole centos to save the time. — Artorias
– Artorias, Commented Dec 30, 2015 at 7:10
If you are trying to create the virtualenv inside a synced folder, it might be a problem with symlinks not being created correctly, as in this question. — user1248490
– user1248490, Commented Dec 30, 2015 at 9:46
yes, it works fine if not in the shared folder. Even though it is the perfect solution, I will just build the venv outside of the shared folder. However, I find another problem when trying to install djangocms-installer(setuptools must be installed to install from a source distribution ) but it is a different problem so I will consider this problem as solved. Thanks. — Artorias
– Artorias, Commented Dec 31, 2015 at 4:20

Diego Bianchi · Accepted Answer · 2020-11-29 09:58:47Z

3

You probably have already a venv, try to delete it with

rm -rf yourPath/venv

and for create a new one

python3 -m venv pathToCreateNewVenv

answered Nov 29, 2020 at 9:58

Diego Bianchi

7527 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Artorias · Accepted Answer · 2015-12-31 04:23:17Z

1

It is probably the problems with symbolic link at shared folder. I solved it by simply create the venv outside of the shared folder.

answered Dec 31, 2015 at 4:23

Artorias

1,0741 gold badge13 silver badges23 bronze badges

Collectives™ on Stack Overflow

[Python]Fail to create virtualenv

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related