I installed embedded python from here, titled \"Windows x86-64 embeddable zip file\", but it does not have pip installed, it does not have site-packages either, when I try t
I recently ran into the same issue. I checked the documentation for pip and they seem to say that this use case isn't supported etc. But anyhow, here is my hack for getting the modules to work.
I installed, and by that I mean unzipped embedded python into a directory called d:\python. I assumed that the modules are going to live in that same directory.
First, to install the pip module, I needed to save the extraceted files. I changed the get-pip.py using a text editor that supported unix line terminators by removing the rmtree lines that remove the temporary and unpacked tree from the blob containted in the get-pip.py file.
I changed both locations, but only the last one was needed. The line that I changed in two locations read
shutil.rmtree(tmpdir, ignore_errors=True)
and I modified it thus (I didn't want to bother with the python indentation blocks):
print('shutil.rmtree(tmpdir, ignore_errors=True)')
I now ran my python D:\python\python.exe on the modified get-pip.py and found the temporary directory where the files were unzipped to.
I copied this directory, (check that it contains a main.py) file into the python install D:\python\pip (this is where I wanted my modules to live), ensuring that the D:\python\pip directory contained the main.py file.
The pip module is now installed in the python directory, but you need to hack pip further to remove the exception above. I did this by changing the locations.py file (in my case located in D:\python\pip\locations.py) to return the bin_py and bin_user locations of D:\python.
ie:
86 if WINDOWS:
....
bin_py = 'd:/python'
bin_user = 'd:/python'
I had to change the user_dir for pip to somewhere that would persist on this drive that was shared across multiple VMs.
The pip module now runs fine, eg
d:\python\python.exe -m pip ...