-
Notifications
You must be signed in to change notification settings - Fork 1
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
Python virtualenv wrapper fns - virtualenv vs venv #49
Comments
More points to note:
|
More notes: This answer to the SO question above recommends venv over everything. A work colleague recommends pyenv (yet another "only one obvious way to do it"). pyenv manages multiple Pythons much like rbenv/Node.js (forked from rbenv) and it has a plugin for virtualenv, called pyenv-virtualenv, which automatically will use It also supports Anaconda/Miniconda. Perhaps I should abandon my wrapperns or switch them to this? |
I'm discovering as I play with Jupyter & matplotlib on a macOS machine, that virtualenv is suboptimal, because it copies Python binaries, which then are no longer macOS Frameworks, and so matplotlib doesn't work when called from inside another application such as a jupyter-enabled virtualenv.
Also tools like MS-VS Code seem to advocate the Python standard virtual environment system (since 3.6) of venv.
Also, I've been using "venv" in my bash fns as a short-hand for "virtualenv" (much like pipenv does, apparently) and so that'll be a bit confusing.
I need to rethink how / if my
mkvenv
,lsvenv
,rmvenv
fns work with virtualenv and venv; maybe switch them to venv and refactor the virtualenv-aware fns tomkpyv
or something?See:
The text was updated successfully, but these errors were encountered: