Skip to content

Examples of ResolutionTooDeep in Pip #13281

@notatallshaw

Description

@notatallshaw

Collecting Examples of ResolutionTooDeep in Pip

This post is not for help, but for collecting examples of where Pip's resolver fails with ResolutionTooDeep. Your contributions will help test future improvements to the resolver's behavior.

What to Include

When submitting an example, please provide the following:

  1. Pip version (pip --version)
  2. Python version (python --version)
  3. Operating System
  4. Output of pip freeze
  5. The exact command that produced the error
  6. Contents of any pyproject.toml, requirements.txt, or other relevant files (if applicable)
    • For pyproject.toml, please include the dependencies value from the [project] section.
    • If the files are too long, you can upload them to a GitHub Gist and share the link.
    • Alternatively, write out any additional steps needed to reproduce the issue.

📝 Example Submission

Pip version: 24.0
Python version: 3.11.6
OS: Ubuntu 22.04

$ pip install mypackage

Output:
ERROR: ResolutionTooDeep: xxx

Output of `pip freeze`:
package-a==1.2.3
package-b==4.5.6
...

Contents of `pyproject.toml`:

[project]
dependencies = [
    "package-a==1.2.3",
    "package-b==4.5.6"
]

(Or link to Gist: https://gist.github.com/your-gist)

Why This Matters

By collecting real-world examples, we can better understand when and why the resolver goes too deep and improve Pip's behavior.

Thank you for helping us make Pip better!

Alternative Solutions

If you need a solution right now you might want to try uv which has a uv pip interface that is similar to pip with a powerful resolver, but there are some compatibility differences.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions