Homebrew-installed Pipenv defaults to Homebrew-created virtualenv Python
See original GitHub issueAs following log, it will use /usr/local/Cellar/pipenv/2018.5.18/libexec/bin/python3.6
, instead of use system installed python
🚀 pipenv install --dev
Warning: the environment variable LANG is not set!
We recommend setting this in ~/.profile (or equivalent) for proper expected behavior.
Creating a virtualenv for this project…
Using /usr/local/Cellar/pipenv/2018.5.18/libexec/bin/python3.6 (3.6.5) to create virtualenv…
⠋Already using interpreter /usr/local/Cellar/pipenv/2018.5.18/libexec/bin/python3.6
Using real prefix '/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6'
New python executable in /Users/aweimeow/pipenv/.venv/bin/python3.6
Also creating executable in /Users/aweimeow/pipenv/.venv/bin/python
Installing setuptools, pip, wheel...done.
Virtualenv location: /Users/aweimeow/pipenv/.venv
Installing dependencies from Pipfile.lock (ae475c)…
Ignoring colorama: markers 'sys_platform == "win32"' don't match your environment
Ignoring configparser: markers 'python_version < "3.2"' don't match your environment
Ignoring enum34: markers 'python_version < "3.4"' don't match your environment
Ignoring funcsigs: markers 'python_version < "3.0"' don't match your environment
Ignoring stdeb: markers 'sys_platform == "linux"' don't match your environment
🐍 ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 55/55 — 00:00:42
To activate this project's virtualenv, run the following:
$ pipenv shell
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Setting up python environment in macOS using Homebrew ...
After stumbling with this problem, I found a perfect solution using two awesome libraries — Pyenv and Pipenv. Pyenv is to manage Python...
Read more >Set python version when creating virtualenv using pipenv
Using a Raspberry Pi using Debian 4.14.34-v7+, I am trying to get pipenv set up with Python 3.6.5 as the default version of...
Read more >Install Python 3.8, Virtual Environments using Pipenv, Django ...
After the installer downloads, open it, and install all the defaults. Verify Installation: Open up Terminal in ( Applications/Utilities/Terminal ) ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Please then remove
brew install pipenv
out of the documentation. I had the same thing where I had to go back to python3.6 and now my homebrew pipenv is broken. Ifpip install
is the preferred way, I’m perfectly happy to do that.I’m having a related issue, I think, wherein Homebrew has installed both
3.6.5
and3.7.0
. With the latter active, running pipenv against the former yields an error:Given the way Homebrew handles this (it unlinks the files in
/usr/local/opt/python/bin/
) I’m not sure there is a good way around the matter. I tried installing brew install pipenv under python 3.6, but it just used homebrew to install and switch to 7, so trying to keep things manually aligned didn’t work either.