About the future of this project

[frostming]

As you might know, pip 19.2.0 introduces a lot of API breaking changes, which are not even mentioned in the release notes. This looks like the maintainers are not expecting other projects relying on the internal interfaces otherwise there are at least deprecation circles.

This is the reason why pip-shims is born, but this project only handles the import redirections and not API changes, which makes it rather difficult to keep track of these changes for downstream projects such as Pipenv and Passa. As with the problem we are facing there are 3 possible solutions:

1. Add support for API changes transition in pip-shims, though I suspect whether it is doable, we will finally find a way I guess.
2. Pin pip version in the setup.py of downstream projects and instruct users to always stick to isolated installation. If so, pip-shims doesn't need to exist anymore.
3. Similar to 2. but vendor a compatible pip into every downstream project that uses internal APIs of pip.

I would like to know your thoughts.

[uranusjr]

Personally I lean toward to just moving parts of pip we need into a new project, and use/maintain that instead (like Pipenv’s notpip but more lean and structured). pip folks expressed that they don’t exclude the possibility to eventually merge the extracted parts back into pip (as a vendored dependency).

[techalchemy]

Hey guys sorry for being so inactive on everything, I have had a lot going on obviously. I am here now and and I am updating this project in the meantime

[brainwane]

@techalchemy has been working on fixing failures (#58) - see some conversation today in this IRC discussion. This is towards unblocking the pipenv release.