Update dependency hypothesis to v6.163.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
hypothesis (changelog)	6.138.14 → 6.163.0

---

Release Notes

HypothesisWorks/hypothesis (hypothesis)

v6.163.0

Compare Source

v6.162.0: Hypothesis version 6.162.0

Compare Source

This release adds support for generating timezone-aware datetimes in
hypothesis.extra.pandas. You can now pass a "DatetimeTZDtype" - such
as ""datetime64[ns, UTC]"" - as the "dtype" of a "series()",
"indexes()", or "column()", and every value will share that single
timezone. The datetime resolution is taken from the dtype, so you can
also generate e.g. ""datetime64[us, UTC]"" columns, and for UTC and
other fixed-offset timezones the generated values cover the full range
representable at that resolution - which for coarser units is far
wider than the "datetime64[ns]" bounds of roughly 1677-2262 (issue
#​4020).

Timezone-aware generation requires pandas >= 2.1. Generated values
include "NaT" unless you pass an elements strategy which excludes it.

The canonical version of these notes (with links) is on readthedocs.

v6.161.8: Hypothesis version 6.161.8

Compare Source

This patch removes a redundant "# pragma: no cover" comment. There is
no user-visible change.

The canonical version of these notes (with links) is on readthedocs.

v6.161.7: Hypothesis version 6.161.7

Compare Source

This patch updates our vendored list of top-level domains, which is
used by the provisional "domains()" strategy.

The canonical version of these notes (with links) is on readthedocs.

v6.161.6: Hypothesis version 6.161.6

Compare Source

This patch improves the display of functions generated by
"functions()". If the "returns=" strategy can only produce a single
value, the function is now shown as a constant lambda such as
"f=lambda x: 3", instead of noting each call to it separately.

We also respect the "repr_pretty()" method of objects which define
one in a few more places, such as the arguments of a failing example.

The canonical version of these notes (with links) is on readthedocs.

v6.161.5: Hypothesis version 6.161.5

Compare Source

This patch fixes a bug where a lambda could be displayed with the
definition of an unrelated lambda which happened to take the same
arguments - for example a function generated by "functions()" when
shown in a failing example.

The canonical version of these notes (with links) is on readthedocs.

v6.161.4: Hypothesis version 6.161.4

Compare Source

We now publish abi3 wheels for Linux armv7l, for both manylinux and
musllinux (issue #​4818).

The canonical version of these notes (with links) is on readthedocs.

v6.161.3: Hypothesis version 6.161.3

Compare Source

This patch improves our internal "@​proxies" decorator, which now
preserves the kind of the decorated function: proxies for async
functions, generator functions, and async generator functions are
themselves functions of the same kind. This prepares for upcoming
"functions()" support (issue #​4149).

The canonical version of these notes (with links) is on readthedocs.

v6.161.2: Hypothesis version 6.161.2

Compare Source

We now publish abi3 wheels for Linux riscv64, for both manylinux and
musllinux (issue #​4815).

The canonical version of these notes (with links) is on readthedocs.

v6.161.1: Hypothesis version 6.161.1

Compare Source

"from_lark()" could generate strings which the grammar's lexer
tokenizes differently than the terminal they were generated for, and
which therefore fail to parse - for example "'"""'" for Lark's built-
in "ESCAPED_STRING" terminal (issue #​4325). Terminal strategies now
only generate strings which the lexer would match in their entirety.

The canonical version of these notes (with links) is on readthedocs.

v6.161.0: Hypothesis version 6.161.0

Compare Source

Values recorded with "note()" are now included in observability
reports, as an ordered list of strings under the "metadata.notes" key
of each test-case observation. Previously, notes were only shown in
the terminal for the minimal failing test case (or for every test
case under "Verbosity.verbose"), and never appeared in observations at
all.

The canonical version of these notes (with links) is on readthedocs.

v6.160.0: Hypothesis version 6.160.0

Compare Source

"Bundle" now supports efficient ".filter()" and ".map()" methods,
which compose with "consumes()" in either order (issue #​3944).
Previously, "consumes(bundle).filter(fn)" could remove rejected values
from the bundle while retrying, and "consumes(bundle.filter(fn))" was
a type error; filtered draws now select among currently-matching
values and consume only the value which was actually drawn.

Thanks to Reagan Lee for the initial implementation of this feature in
pull request #​4084!

The canonical version of these notes (with links) is on readthedocs.

v6.159.0: Hypothesis version 6.159.0

Compare Source

Hypothesis has historically referred to the single execution of a test
function as an "example". However, we have in recent years tended to
call a single execution a "test case" instead, which we think is a
more precise and less overloaded term.

This release updates user-facing documentation, log messages, and
error messages to use the "test case" terminology. Some observability
fields which contain raw strings from Hypothesis might change in
format as a result.

This is not a breaking change, as we have intentionally not changed
any code APIs. In particular, "settings.max_examples" has not been
changed.

The canonical version of these notes (with links) is on readthedocs.

v6.158.1: Hypothesis version 6.158.1

Compare Source

This patch implements filter-rewriting for "times()" and
"datetimes()": simple comparison filters such as
".filter(partial(operator.ge, bound))" are rewritten into efficient
bounds, as "dates()" already did. This includes strategies inferred
from annotated-types bounds like "Annotated[datetime, Gt(...)]", and
contradictory filters now give an empty strategy instead of failing
health checks.

The canonical version of these notes (with links) is on readthedocs.

v6.158.0: Hypothesis version 6.158.0

Compare Source

"datetimes()" now accepts timezone-aware "min_value" and "max_value"
bounds, which are treated as moments in time. In this case "timezones"
defaults to "timezones()", and each generated datetime lies between
the two moments. Passing one aware and one naive bound is an error.

If annotated-types has been imported, the overloaded type hints for
this strategy now distinguish naive from aware datetimes using
"Timezone" metadata.

The canonical version of these notes (with links) is on readthedocs.

v6.157.2: Hypothesis version 6.157.2

Compare Source

This patch continues our migration of Hypothesis internals to rust
(issue #​4740), porting some internal float helpers. There should be no
user-visible change. If you see any change in behavior, please open an
issue.

The canonical version of these notes (with links) is on readthedocs.

v6.157.1: Hypothesis version 6.157.1

Compare Source

Internal refactoring of how "Phase.explain" tracks which parts of a
failing example can vary, with no user-visible change.

The canonical version of these notes (with links) is on readthedocs.

v6.157.0: Hypothesis version 6.157.0

Compare Source

"from_type()" now supports the annotated-types "Timezone" constraint
on "datetime" and "time", resolves the typing-extensions
"TypeAliasType" backport as well as the native form from Python 3.12+,
and suggests subscripting generic aliases like
"annotated_types.LowerCase" if they are mistakenly passed as
"Annotated" metadata.

The canonical version of these notes (with links) is on readthedocs.

v6.156.9: Hypothesis version 6.156.9

Compare Source

This release improves observability output under symbolic backends by
displaying arguments generated by "data()" as "data(...)".

Thanks to zhangli091011 for this fix!

The canonical version of these notes (with links) is on readthedocs.

v6.156.8: Hypothesis version 6.156.8

Compare Source

This patch improves the performance of unique collections drawing from
a fixed pool of elements, such as "sets()" of "sampled_from()", under
symbolic-execution backends such as hypothesis-crosshair.

The canonical version of these notes (with links) is on readthedocs.

v6.156.7: Hypothesis version 6.156.7

Compare Source

This patch fixes a bug where calling ".flatmap()" on a "consumes()"
bundle raised an error (issue #​4427).

The canonical version of these notes (with links) is on readthedocs.

v6.156.6: Hypothesis version 6.156.6

Compare Source

This patch fixes "GitHubArtifactDatabase" failing to download
artifacts due to a colliding "Authorization" header.

The canonical version of these notes (with links) is on readthedocs.

v6.156.5: Hypothesis version 6.156.5

Compare Source

We now publish abi3 wheels for 32-bit linux and 32-bit windows.

The canonical version of these notes (with links) is on readthedocs.

v6.156.4: Hypothesis version 6.156.4

Compare Source

In addition to our version-specific wheels, we now also publish "abi3"
wheels, built against the 3.10 stable ABI.

The canonical version of these notes (with links) is on readthedocs.

v6.156.3: Hypothesis version 6.156.3

Compare Source

Fix not uploading source distributions to PyPI, as of v6.156.0.

v6.156.2: Hypothesis version 6.156.2

Compare Source

This patch fixes a KeyError in |GitHubArtifactDatabase| when reading an
artifact whose zip file contains no explicit directory entries, which is the
case for zips produced by actions/upload-artifact.

v6.156.1: Hypothesis version 6.156.1

Compare Source

This patch fixes our build pipeline from v6.156.0, so that wheels are actually published.

v6.155.7: Hypothesis version 6.155.7

Compare Source

This patch fixes a thread-safety bug where concurrent use of the same
strategy instance could error in rare cases. (issue #​4475).

The canonical version of these notes (with links) is on readthedocs.

v6.155.6: Hypothesis version 6.155.6

Compare Source

This patch replaces some internal "%"-style string formatting with
f-strings. There is no user-visible change.

The canonical version of these notes (with links) is on readthedocs.

v6.155.5: Hypothesis version 6.155.5

Compare Source

"dates()" now raises "InvalidArgument" if a "datetime" is passed as
"min_value" or "max_value". Because "datetime" is a subclass of
"date", such bounds were previously accepted and then failed with a
confusing "TypeError" while generating examples.

The canonical version of these notes (with links) is on readthedocs.

v6.155.4: Hypothesis version 6.155.4

Compare Source

This patch removes a stray "print()" which fired whenever a "dates()"
filter was rewritten.

The canonical version of these notes (with links) is on readthedocs.

v6.155.3: Hypothesis version 6.155.3

Compare Source

When using an alternative backend (such as hypothesis-crosshair),
Hypothesis no longer emits a "test_case" observation for an iteration
that the backend aborts via "BackendCannotProceed" before the test
body runs. Previously such an iteration -- for example when the
crosshair backend has exhausted its search paths -- could surface as a
spurious, draw-less "passed" observation with an empty representation,
even though the engine already discards the iteration entirely.

The canonical version of these notes (with links) is on readthedocs.

v6.155.2: Hypothesis version 6.155.2

Compare Source

This patch rewrites the internal date- and time-drawing helper to use
plain arithmetic instead of branching on the values it draws. The
generated distribution is unchanged, but "dates()", "datetimes()", and
"times()" are now much more efficient under symbolic-execution
backends such as crosshair-tool, which can now solve for a specific
date directly rather than enumerating candidates (issue #​4759).

The canonical version of these notes (with links) is on readthedocs.

v6.155.1: Hypothesis version 6.155.1

Compare Source

Shrinking large floats, strings, and bytestrings is now much faster in
some cases (issue #​4006).

The canonical version of these notes (with links) is on readthedocs.

v6.155.0: Hypothesis version 6.155.0

Compare Source

"from_dtype()" now supports the variable-width string dtype
"numpy.dtypes.StringDType", generating arbitrary strings via "text()"
(issue #​4039).

Additionally, passing a dtype class such as "np.dtypes.StringDType"
where an instance like "np.dtypes.StringDType()" was expected now
raises a clear error, rather than the previous confusing message (or
silent coercion to the object dtype in "arrays()").

The canonical version of these notes (with links) is on readthedocs.

v6.154.2: Hypothesis version 6.154.2

Compare Source

This patch improves the type annotations of "fixed_dictionaries()",
which now accepts a "Mapping" rather than requiring an invariant
"dict". Because the value type is covariant, type-checkers can now
infer the generated type even when the strategies are heterogeneous,
e.g. a "mapping" annotated as "dict[str, SearchStrategy[int] |
SearchStrategy[str]]" (issue #​4665).

The "mapping" and "optional" arguments may now also have different key
and value types, which are unioned in the inferred result.

The canonical version of these notes (with links) is on readthedocs.

v6.154.1: Hypothesis version 6.154.1

Compare Source

This patch fixes a bug where resolving recursive forward references in
"from_type()" (such as "A = list[Union["A", str]]", added in
v6.152.11) could recurse until it hit the interpreter's recursion
limit before falling back to a deferred strategy. Because this
depended on the ambient stack depth, it occasionally surfaced as a
spurious "RecursionError" or other flaky failure. We now break the
cycle eagerly by deferring, so resolution uses a small and constant
amount of stack regardless of how deeply nested the reference is.

The canonical version of these notes (with links) is on readthedocs.

v6.154.0: Hypothesis version 6.154.0

Compare Source

"fixed_dictionaries()" now varies the iteration order of the dicts it
generates, rather than always placing the required keys first, to help
find bugs in code which is sensitive to key order (issue #​3906). If
you need a stable order, we recommend using
"fixed_dictionaries(...).map(stable_sort_function)" or similar.

The canonical version of these notes (with links) is on readthedocs.

v6.153.6: Hypothesis version 6.153.6

Compare Source

The "--hypothesis-show-statistics" report now accounts for the
"Phase.explain" phase separately, rather than including its runtime
and test cases in the "Phase.shrink" phase (issue #​4179).

The canonical version of these notes (with links) is on readthedocs.

v6.153.5: Hypothesis version 6.153.5

Compare Source

This patch dramatically improves the performance of "from_type()" on
hierarchies of abstract classes whose subclasses refer back to the
base class (directly, or via a sibling subclass) in their annotations.
Resolution previously took time cubic in the number of subclasses; we
now resolve each type only once (issue #​4729).

The canonical version of these notes (with links) is on readthedocs.

v6.153.4: Hypothesis version 6.153.4

Compare Source

This patch fixes a bug where fuzz_one_input did not track the
"interesting_origin" of failures (issue #​4420). As a result, it only
saved the single smallest failure to the database rather than the
smallest example of each distinct failure, and the
"interesting_origin" was missing from observability reports.

The canonical version of these notes (with links) is on readthedocs.

v6.153.3: Hypothesis version 6.153.3

Compare Source

This patch fixes a bug where "decimals()" with the "places" argument
could generate values outside the "min_value" and "max_value" bounds,
when those bounds had more fractional digits than "places" (issue
#​4651).

The canonical version of these notes (with links) is on readthedocs.

v6.153.2: Hypothesis version 6.153.2

Compare Source

This patch improves the performance of stateful testing for state
machines with a large number of rules (issue #​4465).

The canonical version of these notes (with links) is on readthedocs.

v6.153.1: Hypothesis version 6.153.1

Compare Source

This patch fixes a bug where we emitted incorrect git patch files when
one file did not have a trailing newline (issue #​4744).

The canonical version of these notes (with links) is on readthedocs.

v6.153.0: Hypothesis version 6.153.0

Compare Source

"event()"'s "payload" is now typed as accepting "Any", matching its
runtime behavior of accepting any string-coercible object.

The canonical version of these notes (with links) is on readthedocs.

v6.152.12: Hypothesis version 6.152.12

Compare Source

When Hypothesis detects that your data generation is flaky and raises
"FlakyStrategyDefinition", the error message now describes what
differed between the two runs - such as a different choice type,
different constraints, or drawing more or less data - as well as the
stack of strategies being drawn from, instead of only reporting that
generation was inconsistent. In stateful tests, it also reports the
steps leading up to the error.

Thanks to Ian Hunt-Isaak for this improvement!

The canonical version of these notes (with links) is on readthedocs.

v6.152.11: Hypothesis version 6.152.11

Compare Source

This patch adds support for recursive forward references in
"from_type()", such as "A = list[Union["A", str]]" (issue #​4542).
Previously, such recursive type aliases would raise a
"ResolutionFailed" error. Now, Hypothesis can automatically resolve
the forward reference by looking it up in the caller's namespace. This
also resolves forward references inside "type[...]", such as
"type["MyClass"]".

The canonical version of these notes (with links) is on readthedocs.

v6.152.10: Hypothesis version 6.152.10

Compare Source

This patch renames our source code directory from "hypothesis-python"
to "hypothesis", and changes our canonical scheme for git tags from
"hypothesis-python-X.Y.Z" to "vX.Y.Z".

We have backfilled git tags in the new "vX.Y.Z" scheme. Any
distributions or build scripts which rely on the git tag scheme should
update to the new scheme.

The canonical version of these notes (with links) is on readthedocs.

v6.152.9

Compare Source

v6.152.8

Compare Source

v6.152.7

Compare Source

v6.152.6

Compare Source

v6.152.5

Compare Source

v6.152.4

Compare Source

v6.152.3

Compare Source

v6.152.2

Compare Source

v6.152.1

Compare Source

v6.152.0

Compare Source

v6.151.14

Compare Source

v6.151.13

Compare Source

v6.151.12

Compare Source

v6.151.11

Compare Source

v6.151.10

Compare Source

v6.151.9

Compare Source

v6.151.8

Compare Source

v6.151.7

Compare Source

v6.151.6

Compare Source

v6.151.5

Compare Source

v6.151.4

Compare Source

v6.151.3

Compare Source

v6.151.2

Compare Source

v6.151.1

Compare Source

v6.151.0

Compare Source

v6.150.3

Compare Source

v6.150.2

Compare Source

v6.150.1

Compare Source

v6.150.0

Compare Source

v6.149.1

Compare Source

v6.149.0

Compare Source

v6.148.13

Compare Source

v6.148.12

Compare Source

v6.148.11

Compare Source

v6.148.10

Compare Source

v6.148.9

Compare Source

v6.148.8

Compare Source

v6.148.7

Compare Source

v6.148.6

Compare Source

v6.148.5

Compare Source

v6.148.4

Compare Source

v6.148.3

Compare Source

v6.148.2

Compare Source

v6.148.1

Compare Source

v6.148.0

Compare Source

v6.147.0

Compare Source

v6.146.0

Compare Source

v6.145.1

Compare Source

v6.145.0

Compare Source

v6.144.1

Compare Source

v6.144.0

Compare Source

v6.143.1

Compare Source

v6.143.0

Compare Source

v6.142.5

Compare Source

v6.142.4

Compare Source

v6.142.3

Compare Source

v6.142.2

Compare Source

v6.142.1

Compare Source

v6.142.0

Compare Source

v6.141.1

Compare Source

v6.141.0

Compare Source

v6.140.4

Compare Source

v6.140.3

Compare Source

v6.140.2

Compare Source

v6.140.1

Compare Source

v6.140.0

Compare Source

v6.139.3

Compare Source

v6.139.2

Compare Source

v6.139.1

Compare Source

v6.139.0

Compare Source

v6.138.17

Compare Source

v6.138.16

Compare Source

v6.138.15

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}