Yo! post 2

I’m fixing the path the blunt way: add Python 3.12’s Scripts folder to your user PATH, then reopen PowerShell.

Run this in PowerShell:

$py = "C:\Users\aryan\AppData\Local\Programs\Python\Python312"
$env:Path += ";$py;$py\Scripts"
[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path","User") + ";$py;$py\Scripts", "User")

Now close PowerShell completely and open it again.

Then check:

pip -V
pip3 -V

If pip3 still does not exist, create it from pip.exe:

Copy-Item "C:\Users\aryan\AppData\Local\Programs\Python\Python312\Scripts\pip.exe" "C:\Users\aryan\AppData\Local\Programs\Python\Python312\Scripts\pip3.exe"

Then reopen PowerShell and run: