➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2016-10-31 09:41 by Anish Patel, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg279774 - (view) | Author: Anish Patel (Anish Patel) | Date: 2016-10-31 09:41 | |
Originally created issue: https://github.com/pypa/pip/issues/4033#issuecomment-256865622 Copied text below: I had already Python 3 installed with the environment variable PYTHONHOME=C:\Program Files\Python35. I attempted to install Python 2, but received this issue (although I was installing python 2 after having installed 3): http://stackoverflow.com/questions/23349957/solving-install-issues-with-python-3-4-on-windows After multiple attempts, I was able to successfully install Python 2 by doing either of following: * Removing the pip feature from Python 2 installation * Removing my PYTHONHOME environment variable and running a complete Python 2 installation Although I resolved my issue, I would like to file this as a bug if it hasn't been filed already. |
|||
| msg279788 - (view) | Author: Steve Dower (steve.dower) *  |
Date: 2016-10-31 13:06 | |
Thanks for the write up. This has already been resolved for 2.7.13 (where install will complete but pip won't be available), and as you discovered you should never set PYTHONHOME (or PYTHONPATH) globally, since it will affect every version and not just the one you intended. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:38 | admin | set | github: 72752 |
| 2016-10-31 13:06:06 | steve.dower | set | status: open -> closed type: crash -> behavior messages: + msg279788 resolution: out of date stage: resolved |
| 2016-10-31 09:41:12 | Anish Patel | create | |