Here are my debugging notes. Still not sure which package is causing the problem, but this does seem to fix it. The error you get when you first run pipenv install with pipenv version 2020.8.13. Traceback (most recent call last): File “/usr/local/bin/pipenv”, line 8, in <module> sys.exit(cli()) File “/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py”, line 829, in __call__ return self.main(*args, … Read more
No, pipenv does not support a minimum python version. Per pipenv issue 1050 feature request on Sep 5, 2018, the pipenv authors have explicitly chosen not to implement it: This is not planned as a feature, not a bug, etc. it is a conscious choice to not pursue it, not simply ‘because it is hard’, … Read more
Removing the virtualenv pip package worked for me (on Ubuntu WSL) pip uninstall virtualenv
Update: pipenv 9.0.0 has been released, which should allow you to use pipenv install -e . as expected. Original answer: pipenv install -e is buggy and has been fixed in master (pull request). It will be available in the next release, sometime after Thanksgiving. Temporary workaround for now is: pipenv shell pip install -e . … Read more
pipenv installs packages in ~/.local/share/virtualenvs/ To find the complete path, you can run pipenv –venv The easiest way to load this into VS Code is to: open the command palette CTRL + SHIFT + P search for Python: Select Interpreter Select the option indicated by PipEnv Full documented steps
Why not simply looking for existing virtual environments? To check where they are stored you can activate one virtual env and get its path: $pipenv shell $pipenv –venv > /path/to/existing_venvs/current_venv ls /path/to/existing_venvs/ > cython-pr4GGvfQ/ openCV-f4drK-E5/ I don’t know if pipenv can store venvs in other places, but at least for me this is enough to … Read more
Here is some documentation on the GitHub repo for pipenv: You can install packages with pipenv from git and other version control systems using URLs formatted according to the following rule: <vcs_type>+<scheme>://<location>/<user_or_organization>/<repository>@<branch_or_tag>#egg=<package_name> So, for example: [packages] requests = {git = “https://github.com/requests/requests.git”, editable = true, ref = “v2.20.1”} You can generate a Pipfile using the command … Read more
What worked for me on Mac OS X Sierra is adding the following into my ~/.bash_profile file: export LANG=”en_US.UTF-8″ export LC_ALL=”en_US.UTF-8″ export LC_CTYPE=”en_US.UTF-8″ Then I reloaded the bash profile with: source ~/.bash_profile For those who use zsh shell, you must add those lines to your ~/.zshrc export LANG=”en_US.UTF-8″ export LC_ALL=”en_US.UTF-8″ export LC_CTYPE=”en_US.UTF-8″ Then I reload … Read more
I had the same problem. You should reinstall pipenv using the same package manager you used the first time. If the installation was done using pip, then: pip uninstall pipenv pip install pipenv If you are using brew, then you must run the commands exposed by Andrei brew uninstall pipenv brew install pipenv To check … Read more
I’m not sure there’s a perfect solution for this, but in the interest of being explicit rather than implicit (PEP 20), I’ve decided to check in a file that needs to be sourced before running any script. This is one extra manual step but you can put this in a Makefile for instance. env.sh export … Read more