My problem was that i recently moved my project with virtualenv to another location, due to this activate script had wrong VIRTUAL_ENV path. $ cat path_to_your_env/bin/activate … # some declarations VIRTUAL_ENV=”/path_to_your_env/bin/python” # <– THIS LINE export VIRTUAL_ENV … # some declarations To fix this, just update VIRTUAL_ENV in activate script. Also you maybe need to … Read more
Typically the steps you always takes are: git clone <repo> cd <repo> pip install virtualenv (if you don’t already have virtualenv installed) virtualenv venv to create your new environment (called ‘venv’ here) source venv/bin/activate to enter the virtual environment pip install -r requirements.txt to install the requirements in the current environment
Useful workaround from the Python bug ticket for anybody else with this issue: Run virtualenv venv –no-setuptools Activate that virtualenv (venv\Scripts\activate) Download and run get-pip.py to manually install pip & setuptools into this virtualenv Continue as normal Alternatively, downgrade to 3.3.3. This should be fixed properly in 3.3.5
You need to have installed the development libraries of OpenSSL. It can be a libssl-dev, libssl-devel if your distribution provides separated packages for the dev libraries. Or install the complete openssl package if they don’t. (venv)➜ src pip install mysql-python==1.2.5 Downloading/unpacking mysql-python==1.2.5 Downloading MySQL-python-1.2.5.zip (108kB): 108kB downloaded Running setup.py (path:/home/braiam/src/venv/build/mysql-python/setup.py) egg_info for package mysql-python Installing … Read more
Try to reinstall using this pip install -U –force-reinstall virtualenv if above solution doesn’t work for you you should create a new virtualenv again because of mojave update
I just set something like this up at work using pip, Fabric and git. The flow is basically like this, and borrows heavily from this script: In our source tree, we maintain a requirements.txt file. We’ll maintain this manually. When we do a new release, the Fabric script creates an archive based on whatever treeish … Read more
As long as you’re moving them from one virtualenv to another on the same machine, you could easily just do: $ cp -r [env1]/lib/pythonX.X/site-packages/* [env2]/lib/pythonX.X/site-packages/ However, if the environments are on different machines or utilizing different versions of python or some other major difference, it’s probably not a good idea. In general it’s much safer … Read more
If you are using a virtual environment just use the following line. pip freeze > requirements.txt It commands to create the requirements file first. Or in dockerfile, RUN pip freeze > requirements.txt .
Short answer, NO. But you can share the venv build scripts. pip freeze all libraries to a requirements.txt file. pip freeze > requirements.txt Create the venv on each OS: python -m venv env source env/bin/activate pip install -r requirements.txt # Install all the libs. There are several reasons why venvs cannot be shared across OSes: … Read more
virtualenv helpers for Windows command shell: virtualenvwrapper-win is a set of DOS-style batch files (doesn’t work in PowerShell). env.py is a single Python2 script (blog post).