pip 19.3 breaks pip2pi 0.8.1 about pip2pi HOT 5 OPEN

I have created a PR that fixes this issue, this commit broke pip2pi pypa/pip@09fd200 as they moved the main function into a main module.

I'm guessing the issue with having a subprocess is that you'd have to know what the alias for pip is, it could be pip or pip3 or pip3.8 or probably pip could not have an alias on the system depending on how it was installed, just a wild guess.

from pip2pi.

I can confirm this. Downgrading is not really an easy option for me.

from pip2pi.

First time trying to run this and encountering this issue too -- considering pip's API isn't public, and that all a quick look at the code seems to suggest is that the implementation here assembles command line arguments, is there a reason that doesn't just get executed as a subprocess (and therefore use pip's public API)?

from pip2pi.

This is probably the best way to call pip as a subprocess:

subprocess.check_call([sys.executable, "-m", "pip", "install", "moduleA", "moduleB"])

from pip2pi.

Created #100 for a longer-term solution.

from pip2pi.