Resolvelib

==================

Bug Fixes
---------

- Fix calls to opaque objects and use provider interface calls instead. `126 <https://github.com/sarugaku/resolvelib/issues/126>`_

==================

Features
--------

- Implement backjumping to significantly speed up the resolution process by skipping over irrelevant parts of the resolution search space. `113 <https://github.com/sarugaku/resolvelib/issues/113>`_

==================

Features
--------

- A new reporter hook ``rejecting_candidate`` is added, replacing ``backtracking``.
The hook is called every time the resolver rejects a conflicting candidate before
trying out the next one in line. `101 <https://github.com/sarugaku/resolvelib/issues/101>`_


Bug Fixes
---------

- Some valid states that were previously rejected are now accepted. This affects
states where multiple candidates for the same dependency conflict with each
other. The ``information`` argument passed to
``AbstractProvider.get_preference`` may now contain empty iterators. This has
always been allowed by the method definition but it was previously not possible
in practice. `91 <https://github.com/sarugaku/resolvelib/issues/91>`_

==================

Features
--------

- A new reporter hook ``resolving_conflicts`` is added. The resolver triggers
this hook when it detects conflicts in the dependency tree, and before it
attempts to fix them. The hook accepts one single argument ``causes``, which
is a list of ``(requirement, parent)`` 2-tuples that represents all the
edges that lead to the detected conflicts. `81 <https://github.com/sarugaku/resolvelib/issues/81>`_

==================

Features
--------

- Add ``backtrack_causes`` to ``get_preference``, which contains information
about the requirements involved in the most recent backtrack. This allows
the provider to utilise this information to tweak the ordering as well as
for recording/reporting conflicts.

==================

Bug Fixes
---------

- When merging a candidate's dependencies, make sure the merge target is
up-to-date within the loop, so the merge does not lose information when a
candidate returns multiple dependency specifications under one identifier
(e.g. specifyiung two dependencies ``a>1`` and ``a<2``, instead of one single
``a>1,<2`` dependency). `80 <https://github.com/sarugaku/resolvelib/issues/80>`_