➜
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 2020-01-29 20:19 by brucelong, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg360984 - (view) | Author: CJ Long (brucelong) | Date: 2020-01-29 20:19 | |
I had Python 3.7 installed on my machine. However, I started having issues with it, so I uninstalled Python. However, when I reinstalled and attempted to run pip from Powershell, the old path was still in my variable, and therefore, could not run pip. Python still works. |
|||
| msg404375 - (view) | Author: Irit Katriel (iritkatriel) *  |
Date: 2021-10-19 23:05 | |
Actually I don't know if this is a windows issue, the report doesn't say. |
|||
| msg404507 - (view) | Author: Steve Dower (steve.dower) * |
Date: 2021-10-20 18:25 | |
It seems like it is, however, it sounds like the OP didn't restart PowerShell after the uninstall or reinstall, which is necessary (though not mentioned, but given it would usually be missed including text to that effect wouldn't have any impact anyway). Basically, the installer correctly sends the system-wide notification that it has updated environment variables. PowerShell ignores it (quite correctly), which means we can't do anything to fix it. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:26 | admin | set | github: 83671 |
| 2021-10-20 18:25:08 | steve.dower | set | status: open -> closed resolution: third party messages: + msg404507 stage: resolved |
| 2021-10-19 23:05:56 | iritkatriel | set | nosy:
+ iritkatriel messages: + msg404375 |
| 2021-10-19 23:05:18 | iritkatriel | set | nosy:
+ tim.golden, steve.dower, zach.ware, paul.moore components: + Windows, - Installation |
| 2020-01-29 20:19:05 | brucelong | create | |