-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
notpip is pip, Vendor in pip==22.2.1, standalone pipenv #5199
Conversation
@@ -9,7 +9,7 @@ | |||
try: | |||
import importlib.metadata as imp_meta | |||
except ImportError: | |||
import pipenv.vendor.importlib_metadata as imp_meta | |||
import importlib_metadata as imp_meta |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We never fail here with ImportError. But it's still confusing that this was changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I recall pondering about it because import pipenv.vendor.importlib_metadata
doesn't exist -- It was confusing to me we would reference a fallabck import that does not exist.
Upstream `pipenv` renamed their internal patched version of `pip` folder to be called `patch.pip`: * pypa/pipenv#5199 So this updates our code as well.
Upstream `pipenv` renamed their internal patched version of `pip` folder to be called `patch.pip`: * pypa/pipenv#5199 So this updates our code as well.
Upstream `pipenv` renamed their internal patched version of `pip` folder to be called `patch.pip`: * pypa/pipenv#5199 So this updates our code as well.
Upstream `pipenv` renamed their internal patched version of `pip` folder to be called `patch.pip`: * pypa/pipenv#5199 So this updates our code as well.
Was branched from and supersedes this PR: #5193
Also supersedes this PR: #5196
which had one failing test that I decided to see if upgrading to the latest pip 22.2 would fix, and it has fixed it locally -- woo-hoo!
Fixes #5188
The issue
This accomplishes the following:
notpip
topip
to be clear that its a patched version ofpip
._post_pip_import.patch
that overrode the standalone pip to be the user installed pip -- and instead go with the patched import to use our vendor'd pip.pip==22.2.1
This will allow for conversion off of some pip-shims, not needing pip installed to use pipenv (or having conflicting versions), and several bug fixes from the vendored dependencies