|
I'll have to do some more experimenting. But including pip3 on Windows seems to be a non-starter right now. I can't even get it to isolate itself from any system installed pip3.
I've renamed the system Scripts directory (where pip lives on Windows), and pip3 still insists on defaulting to the system python's site-directory/pip module. Paths are hardcoded in the binary when it's installed. You can see it by opening pip3.exe in a text editor. I've tried patching the binary, but it only results in errors.
Using pip3 -u or pip3 -t on Windows could result in all dependencies (including one that are already part of Sigil's bundled Python) being installed in the target directory (unless --ignore-dependencies is used). And if there's a compatible system Python already installed, a sigil-supplied pip3 is going to use that to determine which modules are already installed, which dependencies are required, and which dependencies might need upgraded. It's a bit of a mess.
|