Skip to content

Expand on troubleshooting steps in resolver migration guide #9174

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

Merged
merged 1 commit into from
Nov 29, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 15 additions & 4 deletions docs/html/user_guide.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1747,10 +1747,21 @@ How to upgrade and migrate
deliver part of your functionality, please test your integration
with pip 20.3.

4. **Temporarily use the old resolver when necessary.** If you run
into resolution errors and need a workaround while you're fixing
their root causes, you can choose the old resolver behavior
using the flag ``--use-deprecated=legacy-resolver``.
4. **Troubleshoot and try these workarounds if necessary.**

- If pip is taking longer to install packages, read
:ref:`Dependency resolution backtracking` for ways to reduce the
time pip spends backtracking due to dependency conflicts.
- If you don't want pip to actually resolve dependencies, use the
``--no-deps`` option. This is useful when you have a set of package
versions that work together in reality, even though their metadata says
that they conflict. For guidance on a long-term fix, read
:ref:`Fixing conflicting dependencies`.
- If you run into resolution errors and need a workaround while you're
fixing their root causes, you can choose the old resolver behavior using
the flag ``--use-deprecated=legacy-resolver``. This will work until we
release pip 21.0 (see
:ref:`Deprecation timeline for 2020 resolver changes`).

5. **Please report bugs** through the `resolver testing survey`_.

Expand Down