Bump hypothesis from 5.49.0 to 6.0.0

[dependabot]

Bumps hypothesis from 5.49.0 to 6.0.0.

Release notes

Sourced from hypothesis's releases.

Hypothesis for Python - version 6.0.0

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
The canonical version of these notes (with links) is on readthedocs.

Commits

• ba196cb Bump hypothesis-python version to 6.0.0 and update changelog
• d1f56a5 Merge pull request #2744 from Zac-HD/hypothesis-6
• 131c558 Bump hypothesis-ruby version to 0.3.0 and update changelog
• bb270f5 Merge pull request #2680 from amw-zero/helix-rutie-migration
• f1da326 Add changelog
• deaba14 Add release keys
• b3ac612 Commit modifications from check-format task
• 1cc837f Add release file for hypothesis-ruby
• 26f027c Fix rubocop errors
• 45a2bc0 Add ruby tasks back to the CI pipeline
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @astafan8.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[astafan8]

@dependabot merge

[dependabot]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[astafan8]

likely requires replacing fixtures with a context manager within the test. That definitely gives full isolation from other tests (but would probably be much slower). In other words, a test still has the @given but the thing that used to be a fixture would now become a context manager inside the test. (for more info see pytest-dev/pytest#916 (comment) )

another approach is to disable the healthcheck for this explicitly for the tests - https://hypothesis.readthedocs.io/en/latest/healthchecks.html#hypothesis.HealthCheck.function_scoped_fixture and https://hypothesis.readthedocs.io/en/latest/settings.html#hypothesis.settings.suppress_health_check.

[codecov]

Codecov Report

Merging #2601 (d7fade8) into master (6203ce1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2601   +/-   ##
=======================================
  Coverage   63.60%   63.60%           
=======================================
  Files         198      198           
  Lines       25929    25929           
=======================================
  Hits        16493    16493           
  Misses       9436     9436           

[jenshnielsen]

@astafan8 Do you want to fix the too long line length ? otherwise I guess we can merge this one?

[jenshnielsen]

There is also a versioned (and now not working version of hypothesis in environment.yml that we should fix.

Edit: Done