Log Message:
py-hypothesis: updated to 3.71.10

3.71.10:
This patch allows :func:~hypothesis.strategies.from_type to handle the empty \ 
tuple type, :obj:typing.Tuple[()] <python:typing.Tuple>.

3.71.9:
This patch updates some internal comments for :pypi:mypy. There is no \ 
user-visible effect, even for Mypy users.

3.71.8:
This patch fixes a rare bug that would cause a particular shrinker pass to raise \ 
an IndexError, if a shrink improvement changed the underlying data in an \ 
unexpected way.

3.71.7:
This release fixes the broken cross-references in our docs, and adds a CI check \ 
so we don't add new ones.

3.71.6:
This patch fixes two bugs (:issue:944 and :issue:1521), where messages about \ 
:func:@seed <hypothesis.seed> did not check the current verbosity setting, \ 
and the wrong settings were active while executing :ref:explicit examples \ 
<providing-explicit-examples>.

3.71.5:
This patch fixes a DeprecationWarning added in Python 3.8 (:issue:1576).

3.71.4:
This is a no-op release, which implements automatic DOI minting and code \ 
archival of Hypothesis via Zenodo. Thanks to CERN and the EU Horizon 2020 \ 
programme for providing this service!

Check our :gh-file:CITATION file for details, or head right on over to \ 
doi.org/10.5281/zenodo.1412597

3.71.3:
This release adds the test name to some deprecation warnings, for easier debugging.

3.71.2:
This release makes Hypothesis's memory usage substantially smaller for tests \ 
with many examples, by bounding the number of past examples it keeps around.

You will not see much difference unless you are running tests with \ 
:obj:~hypothesis.settings.max_examples set to well over 1000, but if you do have \ 
such tests then you should see memory usage mostly plateau where previously it \ 
would have grown linearly with time.

3.71.1:
This patch adds internal comments to some tree traversals in the core engine. \ 
There is no user-visible change.

3.71.0:
This release deprecates the coverage-guided testing functionality, as it has \ 
proven brittle and does not really pull its weight.

We intend to replace it with something more useful in the future, but the \ 
feature in its current form does not seem to be worth the cost of using, and \ 
whatever replaces it will likely look very different.