Log Message:
py-hypothesis: update to 6.0.1.

6.0.1 - 2021-01-13

This patch fixes an interaction where our test statistics handling
made Pytest’s --junit-xml output fail to validate against the strict
xunit2 schema (issue #1975).

6.0.0 - 2021-01-08

Welcome to the next major version of Hypothesis!

There are no new features here, as we release those in minor
versions. Instead, 6.0 is a chance for us to remove deprecated
features (many already converted into no-ops), and turn a variety
of warnings into errors.

If you were running on the last version of Hypothesis 5.x without
any Hypothesis deprecation warnings, this will be a very boring
upgrade. In fact, nothing will change for you at all.

Changes

    Many functions now use PEP 3102 keyword-only arguments where
    passing positional arguments was deprecated since 5.5.

    hypothesis.extra.django.from_model() no longer accepts model
    as a keyword argument, where it could conflict with fields
    named “model”.

    randoms() now defaults to use_true_random=False.

    complex_numbers() no longer accepts min_magnitude=None; either
    use min_magnitude=0 or just omit the argument.

    hypothesis.provisional.ip4_addr_strings and ip6_addr_strings
    are removed in favor of ip_addresses(v=...).map(str).

    register_type_strategy() no longer accepts generic types with
    type arguments, which were always pretty badly broken.

    Using function-scoped pytest fixtures is now a health-check
    error, instead of a warning.

Tip

The hypothesis codemod command can automatically refactor your
code, particularly to convert positional to keyword arguments where
those are now required.

Hypothesis 5.x

5.49.0 - 2021-01-07

This release adds the function_scoped_fixture health check value,
which can be used to suppress the existing warning that appears
when @given is applied to a test that uses pytest function-scoped
fixtures.

(This warning exists because function-scoped fixtures only run once
per function, not once per example, which is usually unexpected
and can cause subtle problems.)

When this warning becomes a health check error in a future release,
suppressing it via Python warning settings will no longer be
possible. In the rare case that once-per-function behaviour is
intended, it will still be possible to use function_scoped_fixture
to opt out of the health check error for specific tests.

5.48.0 - 2021-01-06

This release adds hypothesis.currently_in_test_context(), which
can be used to check whether the calling code is currently running
inside an @given or stateful test.

This is most useful for third-party integrations and assertion
helpers which may wish to use assume() or target(), without also
requiring that the helper only be used from property-based tests
(issue #2581).

5.47.0 - 2021-01-05

This release upgrades the import logic for ghostwritten tests,
handling many cases where imports would previously be missing or
from unexpected locations.