A couple of things I've realised we need to clearly establish for the packaging user guide are:
Right now, we don't clearly document those environmental assumptions anywhere, which then makes it hard to provide a checklist for people to work through and ensure their environment is set up correctly.
The closest we currently get to this is to include a fairly cursory introduction to virtualenv
in the package installation tutorial, and then implicitly assuming that the following is true in the rest of the guide:
python
will run the desired version of Pythonpip install
and python -m pip install
will be essentially equivalent (aside from the differences when upgrading pip itself on Windows) and install packages into the desired version of PythonThose assumptions are true once you're inside an activated virtual environment, but they're not true in the general case due to the differences between per-user Python installations and system-wide ones, and the differences in cross-platform conventions when it comes to learning how to start Python.
(Issue prompted by https://mail.python.org/pipermail/python-ideas/2017-November/047708.html, #394, and pypa/pip#3164)
Additional related documentation:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4