Potential for confusion on Pipenv & Virtual Environments #840
Comments
|
This part of the guide says that it's written for 3, but will work fine with 2. |
|
I'm not sure that's the issue. Let's say we have a brand new installation of macOS (i.e. we only have a system installation of Python 2.6.x or 2.7.x) and we want to install Python 3. We go here and follow your instructions:
The new Python 3 installation will live wherever Homebrew installed it, and we can access that Python 3 and Pip installation by running
Then, we move onto the virtual environments page... We are told to check to make sure we have Python and Pip installed by running But the problem is, those commands are going to reference the system Python installation and there will be no system Pip installed:
I think the issue which @thepreacher is trying to report, and which had me scratching my head tonight as well, is the mismatch between the instructions given and the actual commands necessary to complete them on a macOS system which uses your suggested Python installation method. |
|
Also, not sure if this should be in a separate issue or not, but after following the Homebrew installation instructions, |
|
This is confused me too on Mac |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

I arrived on the
Pipenv & Virtual Environmentspage fromInstalling Python 3 on Mac OS X. At that point, I've have installed python2 and python3 via homebrew and there is also the system python.Installing Python 3 on Mac OS Xclearly states thatAnd yet on
Pipenv & Virtual Environmentsthe first thing I'm encouraged to do is make sure python3 is installed by typing$python --versionwhich will display the system Python interpreter version.This could potentially confuse a new developer who may be wondering why they are seeing version say
2.7.xinstead of3.6.xas the writeup suggest. Besides as at the time of writting there are not many OS's that have$pythondefaulting to version3.6.x.If the writeup in insisting of starting Python 3 with the command
$pythonthen it needs to be explained how this can be done safely.Thanks.
The text was updated successfully, but these errors were encountered: