-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 fails to create virtual environment from Homebrew-installed Python 3.4.3 #779
Comments
What's your PYTHONPATH look like? It looks like the problem is that your python 3 is loading modules built for python 2.7. |
Seems similar to #705 |
Doing |
This is needed to particularly when a new interpreter is used, via -p/--python. Re-execing the same `virtualenv.py` will generally lead to its path being added to the start of sys.path (as usual). And usually its path will be the site-packages of the previous interpreter. This will lead to issues if older backported packages are present in the old environment (which will then get preference being imported). Should fix pypa#779, pypa#774, pypa#763
@Aarzee would appreciate if you could check if above commit solves the issue https://github.com/Ivoz/virtualenv/archive/early-syspath-removal.zip |
This is needed to particularly when a new interpreter is used, via -p/--python. Re-execing the same `virtualenv.py` will generally lead to its path being added to the start of sys.path (as usual). And usually its path will be the site-packages of the previous interpreter. This will lead to issues if older backported packages are present in the old environment (which will then get preference being imported). Should fix pypa#779, pypa#774, pypa#763
Unfortunately, yesterday I upgraded to El Capitan, and pyenv is failing to install 3.4.3 (which is now unavailable via Homebrew). I can't reproduce the bug with current PyPI virtualenv when making a Python 3.5 environment. |
This is needed particularly when a new interpreter is used, via -p/--python. Re-execing the same `virtualenv.py` will generally lead to its path being added to the start of sys.path (as usual). And usually its path will be the site-packages of the previous interpreter. This will lead to issues if older backported packages are present in the old environment (which will then get preference being imported). Should fix pypa#779, pypa#774, pypa#763
I'm having the exact same issue, can someone please reopen?
Other details:
|
Problem solved, it was due to Homebrew. It was solved with the following commands:
After that, |
On Mon, Sep 26, 2016, 09:22 Vincent Marquet notifications@github.com
|
No, I tried |
Sadly I am still getting this error, command I am firing off: Error:
I tried
Same error.
Thoughts? |
Okay, problem found, it was the
worked fine. |
A different solution worked for me. I'm using Mac OS X 10.12.3 and python3.5 installed from a package obtained from python.org.
|
When I try to create a virtual environment with Python 3.4.3,
virtualenv
errors out:I've found another reference to the exact same error on StackOverflow, with the only answer suggesting to add the
--no-site-packages
argument. Looking throughvirtualenv -h
, I see that not only is it deprecated, it doesn't change the setting, as its functionality is currently the default. Predictably, this does not help.The text was updated successfully, but these errors were encountered: