Skip to content

Regression updating dependencies in 2025.0.3 - ResolutionTooDeepError #6415

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

Open
ipmb opened this issue May 30, 2025 · 1 comment
Open

Regression updating dependencies in 2025.0.3 - ResolutionTooDeepError #6415

ipmb opened this issue May 30, 2025 · 1 comment

Comments

@ipmb
Copy link

ipmb commented May 30, 2025

Issue description

Updating dependencies fails with a ResolutionTooDeepError error

Expected result

It succeeds. Here is an example from the previous version: https://github.com/lincolnloop/python-package-manager-shootout/actions/runs/15331237636/job/43138278387

Actual result

To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (247cab)...
All dependencies are now up-to-date!
Upgrading  in  dependencies.
Building requirements...
Resolving dependencies...
Locking Failed!
Traceback (most recent call last):
  File "/home/runner/.local/lib/python3.11/site-packages/pipenv/resolver.py", 
line 465, in <module>
    main()
  File "/home/runner/.local/lib/python3.11/site-packages/pipenv/resolver.py", 
line 451, in main
    _main(
  File "/home/runner/.local/lib/python3.11/site-packages/pipenv/resolver.py", 
line 436, in _main
    resolve_packages(
  File "/home/runner/.local/lib/python3.11/site-packages/pipenv/resolver.py", 
line 400, in resolve_packages
    results, resolver = resolve_deps(
                        ^^^^^^^^^^^^^
  File 
"/home/runner/.local/lib/python3.11/site-packages/pipenv/utils/resolver.py", 
line 979, in resolve_deps
    results, hashes, internal_resolver = actually_resolve_deps(
                                         ^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/runner/.local/lib/python3.11/site-packages/pipenv/utils/resolver.py", 
line 747, in actually_resolve_deps
    resolver.resolve()
  File 
"/home/runner/.local/lib/python3.11/site-packages/pipenv/utils/resolver.py", 
line 472, in resolve
    results = resolver.resolve(self.constraints, check_supported_wheels=False)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/home/runner/.local/lib/python3.11/site-packages/pipenv/patched/pip/_internal/r
esolution/resolvelib/resolver.py", line 107, in resolve
    raise ResolutionTooDeepError from None
pipenv.patched.pip._internal.exceptions.ResolutionTooDeepError: 
<ResolutionTooDeepError: resolution-too-deep>

Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Failed to lock Pipfile.lock!

Steps to replicate

You can see the steps taken here, https://github.com/lincolnloop/python-package-manager-shootout/actions/runs/15347384043/job/43186661701

@julio-tl
Copy link

julio-tl commented Jun 4, 2025

@ipmb We are noticing similar errors but I narrowed it down to a google dependency we pull for our Airflow project on MWAA:

apache-airflow-providers-google = "==10.19.0"

Edit: I think it's due to a breaking change reported here: googleapis/python-spanner-sqlalchemy#682

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants