Log message:
py-hypothesis: updated to 3.44.26

3.44.26:
This release fixes some formatting issues in the Hypothesis source code. It \ 
should have no externally visible effects.

3.44.25:
This release changes the way in which Hypothesis tries to shrink the size of \ 
examples. It probably won't have much impact, but might make shrinking faster in \ 
some cases. It is unlikely but not impossible that it will change the resulting \ 
examples.

Log message:
py-hypothesis: updated to 3.44.24

3.44.24:
This release fixes dependency information when installing Hypothesis from a \ 
binary "wheel" distribution.
The install_requires for enum34 is resolved at install time, rather than at \ 
build time (with potentially different results).
Django has fixed their python_requires for versions 2.0.0 onward, simplifying \ 
Python2-compatible constraints for downstream projects.

Log message:
py-hypothesis: updated to 3.44.16

3.44.16:
This release improves test case reduction for recursive data structures. \ 
Hypothesis now guarantees that whenever a strategy calls itself recursively \ 
(usually this will happen because you are using \ 
~hypothesis.strategies.deferred), any recursive call may replace the top level \ 
value. e.g. given a tree structure, Hypothesis will always try replacing it with \ 
a subtree.

Additionally this introduces a new heuristic that may in some circumstances \ 
significantly speed up test case reduction - Hypothesis should be better at \ 
immediately replacing elements drawn inside another strategy with their minimal \ 
possible value.

3.44.15:
~hypothesis.strategies.from_type can now resolve recursive types such as binary \ 
trees. Detection of non-type arguments has also improved, leading to better \ 
error messages in many cases involving

3.44.14:
This release fixes a bug in the shrinker that prevented the optimisations in \ 
3.44.6 from working in some cases. It would not have worked correctly when \ 
filtered examples were nested (e.g. with a set of integers in some range).

This would not have resulted in any correctness problems, but shrinking may have \ 
been slower than it otherwise could be.

3.44.13:
This release changes the average bit length of values drawn from \ 
~hypothesis.strategies.integers to be much smaller. Additionally it changes the \ 
shrinking order so that now size is considered before sign - e.g. -1 will be \ 
preferred to +10.

The new internal format for integers required some changes to the minimizer to \ 
make work well, so you may also see some improvements to example quality in \ 
unrelated areas.

3.44.12:
This changes Hypothesis's internal implementation of weighted sampling. This \ 
will affect example distribution and quality, but you shouldn't see any other \ 
effects.

3.44.11:
This is a change to some internals around how Hypothesis handles avoiding \ 
generating duplicate examples and seeking out novel regions of the search space.

You are unlikely to see much difference as a result of it, but it fixes a bug \ 
where an internal assertion could theoretically be triggered and has some minor \ 
effects on the distribution of examples so could potentially find bugs that have \ 
previously been missed.

3.44.10:
This patch avoids creating debug statements when debugging is disabled. \ 
Profiling suggests this is a 5-10% performance improvement

Log message:
py-hypothesis: updated to 3.44.4

3.44.4:
This release fixes :issue:1044, which slowed tests by up to 6% due to broken caching.

Log message:
py-hypothesis: updated to 3.44.3

3.44.3:
This release improves the shrinker in cases where examples drawn earlier can \ 
affect how much data is drawn later (e.g. when you draw a length parameter in a \ 
composite and then draw that many elements). Examples found in cases like this \ 
should now be much closer to minimal.

3.44.2:
This is a pure refactoring release which changes how Hypothesis manages its set \ 
of examples internally. It should have no externally visible effects.

3.44.1:
This release fixes :issue:`997`, in which under some circumstances the body of \ 
tests run under Hypothesis would not show up when run under coverage even though \ 
the tests were run and the code they called outside of the test file would show \ 
up normally.

3.44.0:
This release adds a new feature: The :ref:`@reproduce_failure \ 
<reproduce_failure>`, designed to make it easy to use Hypothesis's binary \ 
format for examples to reproduce a problem locally without having to share your \ 
example database between machines.

This also changes when seeds are printed:

They will no longer be printed for normal falsifying examples, as there are now \ 
adequate ways of reproducing those for all cases, so it just contributes noise.
They will once again be printed when reusing examples from the database, as \ 
health check failures should now be more reliable in this scenario so it will \ 
almost always work in this case.

Log message:
py-hypothesis: updated to 3.42.2

3.42.2:
This patch fixes :issue:1017, where instances of a list or tuple subtype used as \ 
an argument to a strategy would be coerced to tuple.

3.42.1:
This release has some internal cleanup, which makes reading the code more \ 
pleasant and may shrink large examples slightly faster.

3.42.0:
This release deprecates :ref:faker-extra, which was designed as a transition \ 
strategy but does not support example shrinking or coverage-guided discovery.

Log message:
py-hypothesis: updated to 3.37.0

3.37.0:
This is a deprecation release for some health check related features.

The following are now deprecated:

* Passing exception_in_generation to suppress_health_check. This no longer does \ 
anything even when passed - All errors that occur during data generation will \ 
now be immediately reraised rather than going through the health check \ 
mechanism.

* Passing random_module to suppress_health_check. This hasn’t done anything \ 
for a long time, but was never explicitly deprecated. Hypothesis always seeds \ 
the random module when running @given tests, so this is no longer an error and \ 
suppressing it doesn’t do anything.

* Passing non-HealthCheck values in suppress_health_check. This was previously \ 
allowed but never did anything useful.

In addition, passing a non-iterable value as suppress_health_check will now \ 
raise an error immediately (it would never have worked correctly, but it would \ 
previously have failed later). Some validation error messages have also been \ 
updated.

Log message:
py-hypothesis: updated to 3.36.0

3.36.0:
This release adds a setting to the public API, and does some internal cleanup:
The :attr:`~hypothesis.settings.derandomize` setting is now documented
Removed - and disallowed - all 'bare excepts' in Hypothesis
Documented the :attr:`~hypothesis.settings.strict` setting as deprecated, and \ 
updated the build so our docs always match deprecations in the code.

Log message:
py-hypothesis: updated to 3.34.1

3.34.1:

This patch updates the documentation to suggest :func:`builds(callable) \ 
<hypothesis.strategies.builds>` instead of :func:`just(callable()) \ 
<hypothesis.strategies.just>`.

3.34.0:

Hypothesis now emits deprecation warnings if you apply :func:`@given \ 
<hypothesis.given>` more than once to a target.

Applying :func:`@given <hypothesis.given>` repeatedly wraps the target \ 
multiple times. Each wrapper will search the space of of possible parameters \ 
separately. This is equivalent but will be much more inefficient than doing it \ 
with a single call to :func:`@given <hypothesis.given>`.

For example, instead of @given(booleans()) @given(integers()), you could write \ 
@given(booleans(), integers())

Log message:
py-hypothesis: updated to 3.33.1

3.33.1:

This is a bugfix release:
* :func:`~hypothesis.strategies.builds` would try to infer a strategy for \ 
required positional arguments of the target from type hints, even if they had \ 
been given to :func:`~hypothesis.strategies.builds` as positional arguments \ 
(:issue:`946`). Now it only infers missing required arguments.
* An internal introspection function wrongly reported self as a required \ 
argument for bound methods, which might also have affected \ 
:func:`~hypothesis.strategies.builds`. Now it knows better.