Skip to content
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

Makefile bug #25

Open
jlpeabody opened this issue Jun 6, 2021 · 0 comments
Open

Makefile bug #25

jlpeabody opened this issue Jun 6, 2021 · 0 comments

Comments

@jlpeabody
Copy link

Using python2 to install a python3 environment has been problematic for some time now.

Example:
$ virtualenv -p python3 env

Invokes python2 virtualenv which imports the now deprecated emp module.

I better way to install a python3 virtual environment might be (adapted to match match this repo's expectations):
python3 -m venv env

Additionally, pip should be run from within the environment and upgraded upon its initial invocation. Reason being is that not all *nux distros have upgraded to python3 yet so without switching to the newly created vitual environment first might invoke pip2 not pip3. It is almost a forgone conclusion that when the virtual environment is created it will have an old version of pip3 installed in it and if it is invoked, it will toss warnings until upgraded.

a reasonable couple lines like:
source /env/bin/activate pip install --upgrade pip

Then finally the most reasonable:
pip install -r requirements/base.txt

*NOTE I didn't qualify pip in assuming that the virtualenv would still be active.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant