There are two options I’m aware of. One, change the PYTHONPATH environment variable to include the directory above your module. Alternatively, edit ~/.pylintrc to include the directory above your module, like this: [MASTER] init-hook=’import sys; sys.path.append(“/path/to/root”)’ (Or in other version of pylint, the init-hook requires you to change [General] to [MASTER]) Both of these options … Read more
Conda replaces virtualenv. In my opinion it is better. It is not limited to Python but can be used for other languages too. In my experience it provides a much smoother experience, especially for scientific packages. The first time I got MayaVi properly installed on Mac was with conda. You can still use pip. In … Read more
If you happen to be using the venv module that comes with Python 3.3+, it supports an –upgrade option. Per the docs: Upgrade the environment directory to use this version of Python, assuming Python has been upgraded in-place python3 -m venv –upgrade ENV_DIR
You should be able to do this by using the python in your virtual environment: /home/my/virtual/bin/python /home/my/project/manage.py command arg EDIT: If your django project isn’t in the PYTHONPATH, then you’ll need to switch to the right directory: cd /home/my/project && /home/my/virtual/bin/python … You can also try to log the failure from cron: cd /home/my/project && … Read more
If you installed it with pip install virtualenv You need to run sudo /usr/bin/easy_install virtualenv which puts it in /usr/local/bin/. The above directory by default should be in your PATH; otherwise, edit your .zshrc (or .bashrc) accordingly.
Here is my workflow after creating a folder and cd‘ing into it: $ virtualenv venv –distribute New python executable in venv/bin/python Installing distribute………done. Installing pip…………….done. $ source venv/bin/activate (venv)$ python
pip defaults to installing Python packages to a system directory (such as /usr/local/lib/python3.4). This requires root access. –user makes pip install packages in your home directory instead, which doesn’t require any special privileges.
The gcc compiler is not in your $PATH. It means either you dont have gcc installed or it’s not in your $PATH variable. To install gcc use this: (run as root) Redhat base: yum groupinstall “Development Tools” Debian base: apt-get install build-essential openSUSE base: zypper install –type pattern devel_basis Alpine: apk add build-base
This is very good: http://simononsoftware.com/virtualenv-tutorial-part-2/ And this is a slightly more practical one: https://web.archive.org/web/20160404222648/https://iamzed.com/2009/05/07/a-primer-on-virtualenv/
I use pip freeze to get the packages I need into a requirements.txt file and add that to my repository. I tried to think of a way of why you would want to store the entire virtualenv, but I could not.