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.
Discrepancy in Installation Python 3 on Windows #846
Comments
|
pull requests accepted! |
|
Since both pip and pipenv can be run as > py -m pip --version
pip 9.0.1 from C:\Users\twwilliams\AppData\Local\Programs\Python\Python36\lib\site-packages (python 3.6)
> py -2 -m pip --version
pip 9.0.1 from C:\Users\twwwilliams\.windows-build-tools\python27\lib\site-packages (python 2.7)I will try to take some time over the holiday to put together a pull request to address this. |
|
I think this has been resolved by making Python 3 the default version in the guide and assuming |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Working with Python 3 section mentions you should use
python3to launch the Python 3 interpreter, which does not actually work. The Windows distribution provides onlypython.exefor all versions of Python, and to launch the Python 3 interpreter you needpython. This also creates problems if you install both Python 2 and 3—the executables override each other, and only one of the exes is visible at a time through%Path%(what actually is visible depends on the order of the search paths).AFAIK the official way to deal with this problem is through the py launcher, but that only solves the
python.exeproblem, not other scripts installed later during the setup (e.g. pip vs pip3), and other global tools (e.g. pipenv). It will affect other parts of the tutorial as well.The text was updated successfully, but these errors were encountered: