Log Message:
py-hypothesis: updated to 4.7.17

4.7.17:
This release makes some micro-optimisations within Hypothesis's internal \ 
representation of test cases. This should cause heavily nested test cases to \ 
allocate less during generation and shrinking, which should speed things up \ 
slightly.

4.7.16:
This changes the order in which Hypothesis runs certain operations during \ 
shrinking. This should significantly decrease memory usage and speed up \ 
shrinking of large examples.

4.7.15:
This release allows Hypothesis to calculate a number of attributes of generated \ 
test cases lazily. This should significantly reduce memory usage and modestly \ 
improve performance, especially for large test cases.

4.7.14:
This release reduces the number of operations the shrinker will try when \ 
reordering parts of a test case. This should in some circumstances significantly \ 
speed up shrinking. It may result in different final test cases, and if so \ 
usually slightly worse ones, but it should not generally have much impact on the \ 
end result as the operations removed were typically useless.

4.7.13:
This release changes how Hypothesis reorders examples within a test case during \ 
shrinking. This should make shrinking considerably faster.

4.7.12:
This release slightly improves the shrinker's ability to replace parts of a test \ 
case with their minimal version, by allowing it to do so in bulk rather than one \ 
at a time. Where this is effective, shrinker performance should be modestly \ 
improved.

4.7.11:
This release makes some micro-optimisations to common operations performed \ 
during shrinking. Shrinking should now be slightly faster, especially for large \ 
examples with relatively fast test functions.

4.7.10:
This release is a purely internal refactoring of Hypothesis's API for \ 
representing test cases. There should be no user visible effect.

4.7.9:
This release changes certain shrink passes to make them more efficient when they \ 
aren't making progress.

4.7.8:
This patch removes some unused code, which makes the internals a bit easier to \ 
understand. There is no user-visible impact.

4.7.7:
This release reduces the number of operations the shrinker will try when \ 
reordering parts of a test case. This should in some circumstances significantly \ 
speed up shrinking. It may result in different final test cases, and if so \ 
usually slightly worse ones, but it should not generally have much impact on the \ 
end result as the operations removed were typically useless.

4.7.6:
This patch removes some unused code from the shrinker. There is no user-visible \ 
change.

4.7.5:
This release changes certain shrink passes to make them adaptive - that is, in \ 
cases where they are successfully making progress they may now do so \ 
significantly faster.

4.7.4:
This is a docs-only patch, noting that because the :pypi:lark-parser is under \ 
active development at version 0.x, hypothesis[lark] APIs may break in minor \ 
releases if necessary to keep up with the upstream package.

4.7.3:
This changes Hypothesis to no longer import various test frameworks by default \ 
(if they are installed). which will speed up the initial import hypothesis call.

4.7.2:
This release changes Hypothesis's internal representation of a test case to \ 
calculate some expensive structural information on demand rather than eagerly. \ 
This should reduce memory usage a fair bit, and may make generation somewhat \ 
faster.

4.7.1:
This release refactors the internal representation of previously run test cases. \ 
The main thing you should see as a result is that Hypothesis becomes somewhat \ 
less memory hungry.

4.7.0:
This patch allows :func:~hypothesis.extra.numpy.array_shapes to generate shapes \ 
with side-length or even dimension zero, though the minimum still defaults to \ 
one. These shapes are rare and have some odd behavior, but are particularly \ 
important to test for just that reason!

In a related bigfix, :func:~hypothesis.extra.numpy.arrays now supports \ 
generating zero-dimensional arrays with dtype=object and a strategy for iterable \ 
elements. Previously, the array element would incorrectly be set to the first \ 
item in the generated iterable.