-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Upgrading an environment started from 2 base packages fails (only) with new resolver #9572
Comments
This may be a good test case for the related issue #4551. |
That’s basically what the new resolver is good for, it catches and prevents the inconsistent state from ever happening. You would end up with an inconsistent state after upgrading, so it refuses to upgrade and keep your environment in a consistent state. Everything seems to work as designed, from what I can tell. |
@uranusjr I am not sure I agree. I will verify, but my understanding is that
This may be two issues coming together: unwanted downgrade plus installation failure. But I would not say everything is working as planned. |
and with
As a human, I see from |
TLDR:
fails while trying to install very old packages although newer packages are available. The command above is obtained from installing just two packages and then trying to upgrade all installed packages.
gives (for all pip versions I tested):
Some time later, I try to upgrade my installation. I usually do this because pip is not yet able to consider installed packages:
which gives (again, for all versions)
Running this command with pip 20.2.3 works, although it's ends up with an incompatible state:
While running it with 21.0.1 and today's 21.1.dev0 gives this:
Given that the environment is in a consistent state with all dependencies fulfilled, I'd say a better behvaior for this upgrade command (than to downgrade to
textract==0.5.1
, which is the first error) would be to do nothing. (I do see how that may be difficult given that pip does not take installed packages into account.)The text was updated successfully, but these errors were encountered: