What distro/OS are you using? That process can sometimes have issues if you’re on a OS that includes a preinstalled version of Python. In those cases, I would recommend checking the official repository it uses to see if there’s a python3-pip or similar package to install pip through (if it’s not already installed).
Since the installation failed to even create the first directory, there shouldn’t be anything installed on the system by the script you’ve run. The script could have saved some files in a ~/.cache, but looking at the output, it didn’t cache anything. pip does cleanup after itself pretty well (eg. even deleting temporary directories it makes before exiting).
So… no, I don’t think there’s anything for you to do here manually.
Thanks for reaching out and checking in with us over here! ^>^
So I checked ~/.cache and found the pip directory. I deleted it and rerun python get-pip.py.
The script failed again (like it did initially) and again I was left with ~/.cache/pip. So get-pip.py does indeed leave some files though I wouldn’t consider this a problem since ~/.cache is a folder that people are allowed to remove.