sarugaku / resolvelib

Resolve abstract dependencies into concrete ones

sarugaku/resolvelib Issues

Request: New Release
Closed a month ago19
sdist is missing conftest.py
Closed 13 days ago1
Release 1.1.0 Broke Build Pipelines
Closed 13 days ago7
Causes returned by `_attempt_to_pin_criterion` are too broad (causing searching unnecessary parts of a dependency graph)
Updated 14 days ago6
Request: New Final Release
Closed 14 days ago
An example of resolution failure while it does have a valid resolution.
Closed 5 months ago33
Use pip-resolver-benchmarks and Pip code to create "real world" resolvelib tests?
Closed 5 months ago3
For n packages there are O(n^2) calls to `_is_current_pin_satisfying`
Updated 10 months ago4
Idea: Breadth-first search until reaching breadth level with unpinned requirements
Updated a year ago
Add documentation
Updated a year ago5
“Learn” to avoid trying routes that do not affect the dependency graph
Updated a year ago49
Option to only provide causes of conflict when calling get_preference
Updated a year ago2
Implement Causes Narrowing
Closed a year ago1
Awkward wording in docstring for `find_matches()`
Closed a year ago5
ResolveLib 2.0 and unsupported Pythons
Updated 2 years ago5
Required Python versions not specified in pip-readable way
Closed 2 years ago1
Toward 1.0
Closed 2 years ago12
Please make a new release
Closed 2 years ago
0.9.0: pytest is failing in 6 units
Closed 2 years ago3
Resolvelib 0.9.0 passes identifiers to Provider's `get_preference` method without accompanying PreferenceInformation
Closed 2 years ago5
Add CoC
Closed 2 years ago1
Drop support for Python prior to 3.7
Closed 2 years ago3
Test Failures With Packaging 22.0/23.0
Closed 2 years ago1
Default branch has been renamed to `main` and branch protections enabled
Closed 2 years ago
0.8.1: pytest warnings
Closed 2 years ago3
criteria compatibility check while backtracking includes dependencies for version we're backtracking on
Closed 2 years ago26
Sdist releases on pypi.org do not contain files required for tests
Closed 2 years ago2
Let's move this to the `pypa` organisation?
Closed 2 years ago4
Implement lazy consumption of the candidates iterable returned by find_matches()
Closed 2 years ago1
Typing inconsistency: `AbstractProvider.get_preferences`
Closed 3 years ago1
Backtrack on inconsistent candidate
Closed 3 years ago3
resolvelib 0.6.0 and pip vendoring
Closed 3 years ago4
find_matches() got an unexpected keyword argument 'identifier'
Closed 3 years ago8
Add info about how to run tests to README
Closed 3 years ago2
Add a candidate validation step
Closed 3 years ago11
Upcoming breaking changes
Closed 4 years ago
Candidate filtering depends on candidate equality logic implicitly
Closed 4 years ago6
Breaking change in 0.5.5
Closed 4 years ago2
Lazy-evaluate `is_satisfied_by`
Closed 4 years ago2
KeyError: 'dictionary is empty' during backtracking
Closed 4 years ago1
Provider.find_matches shoudn't be called while adding initial requirements
Updated 4 years ago2
Missing git tag for 0.5.1 release
Closed 4 years ago1
Improve README to better summarise the different names and concepts
Updated 4 years ago2
Resolving depends on the order of the root requirements in some cases
Closed 5 years ago5
Make it possible (for a reporter) to determine which candidate a requirement originates from
Closed 5 years ago9
Investigate adding property-based testing?
Updated 5 years ago
Investigate failing PyPI tests
Closed 5 years ago1
Confusing abstraction 'ExtrasProvider'
Updated 5 years ago2
resolution fails for 'django'
Closed 5 years ago3
`find_matches` is underspecified - duplicate candidates
Updated 5 years ago4