NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #384 most downloaded on PyPI
The property-based testing library for Python
Latest stable
6.170.17
Last release 2 days ago
20 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
1596 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
"datetimes()" now accepts timezone-aware "min_value" and "max_value" bounds, which are treated as moments in time. In this case "timezones" defaults t
"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.
~hypothesis.strategies.datetimes now accepts timezone-aware min_value and max_value bounds, which are treated as moments in time. In this case timezones defaults to ~hypothesis.strategies.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.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This patch continues our migration of Hypothesis internals to rust (issue #4740), porting some internal float helpers. There should be no user-visible
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.
Internal refactoring of how "Phase.explain" tracks which parts of a failing example can vary, with no user-visible change.
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.
Internal refactoring of how |Phase.explain| tracks which parts of a failing example can vary, with no user-visible change.
"from_type()" now supports the annotated-types "Timezone" constraint on "datetime" and "time", resolves the typing-extensions "TypeAliasType" backport
"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.
~hypothesis.strategies.from_type now supports the annotated-types Timezone constraint on ~python:datetime.datetime and ~python:datetime.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.
This release improves observability output under symbolic backends by displaying arguments generated by "data()" as "data(...)".
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.
This release improves observability output under symbolic backends by displaying arguments generated by ~hypothesis.strategies.data as data(...).
Thanks to zhangli091011 for this fix!
This patch improves the performance of unique collections drawing from a fixed pool of elements, such as "sets()" of "sampled_from()", under symbolic-
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.
This patch improves the performance of unique collections drawing from a fixed pool of elements, such as ~hypothesis.strategies.sets of ~hypothesis.strategies.sampled_from, under symbolic-execution backends such as hypothesis-crosshair.
This patch fixes a bug where calling ".flatmap()" on a "consumes()" bundle raised an error (issue #4427).
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.
This patch fixes a bug where calling .flatmap() on a ~hypothesis.stateful.consumes bundle raised an error (4427).
This patch fixes "GitHubArtifactDatabase" failing to download artifacts due to a colliding "Authorization" header.
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.
This patch fixes |GitHubArtifactDatabase| failing to download artifacts due to a colliding Authorization header.
We now publish abi3 wheels for 32-bit linux and 32-bit windows.
We now publish abi3 wheels for 32-bit linux and 32-bit windows.
The canonical version of these notes (with links) is on readthedocs.
In addition to our version-specific wheels, we now also publish "abi3" wheels, built against the 3.10 stable ABI.
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.
In addition to our version-specific wheels, we now also publish abi3 wheels, built against the 3.10 stable ABI.
Fix not uploading source distributions to PyPI, as of v6.156.0.
Fix not uploading source distributions to PyPI, as of v6.156.0.
This patch fixes a KeyError in |GitHubArtifactDatabase| when reading an artifact whose zip file contains no explicit directory entries, which is the c
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.
This patch fixes our build pipeline from v6.156.0, so that wheels are actually published.
This patch fixes our build pipeline from v6.156.0, so that wheels are actually published.
This patch fixes our build pipeline from 6.156.0, so that wheels are actually published.
This patch fixes a thread-safety bug where concurrent use of the same strategy instance could error in rare cases. (issue #4475).
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.
This patch fixes a thread-safety bug where concurrent use of the same strategy instance could error in rare cases. (4475).
This patch replaces some internal "%"-style string formatting with f-strings. There is no user-visible change.
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.
This patch replaces some internal %-style string formatting with f-strings. There is no user-visible change.
"dates()" now raises "InvalidArgument" if a "datetime" is passed as "min_value" or "max_value". Because "datetime" is a subclass of "date", such bound
"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.
~hypothesis.strategies.dates now raises InvalidArgument if a ~python:datetime.datetime is passed as min_value or max_value. Because datetime is a subclass of ~python:datetime.date, such bounds were previously accepted and then failed with a confusing TypeError while generating examples.
This patch removes a stray "print()" which fired whenever a "dates()" filter was rewritten.
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.
This patch removes a stray print() which fired whenever a |st.dates| filter was rewritten.
When using an alternative backend (such as hypothesis-crosshair), Hypothesis no longer emits a "test_case" observation for an iteration that the backe
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.
This patch rewrites the internal date- and time-drawing helper to use plain arithmetic instead of branching on the values it draws. The generated dist
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.
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 ~hypothesis.strategies.dates, ~hypothesis.strategies.datetimes, and ~hypothesis.strategies.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 (4759).
Shrinking large floats, strings, and bytestrings is now much faster in some cases (issue #4006).
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.
Shrinking large floats, strings, and bytestrings is now much faster in some cases (4006).
"from_dtype()" now supports the variable-width string dtype "numpy.dtypes.StringDType", generating arbitrary strings via "text()" (issue #4039).
"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.
~hypothesis.extra.numpy.from_dtype now supports the variable-width string dtype numpy:numpy.dtypes.StringDType, generating arbitrary strings via ~hypothesis.strategies.text (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 ~hypothesis.extra.numpy.arrays).
This patch improves the type annotations of "fixed_dictionaries()", which now accepts a "Mapping" rather than requiring an invariant "dict". Because t
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.
This patch improves the type annotations of |st.fixed_dictionaries|, which now accepts a ~collections.abc.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]] (4665).
The mapping and optional arguments may now also have different key and value types, which are unioned in the inferred result.
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 r
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.
This patch fixes a bug where resolving recursive forward references in |st.from_type| (such as A = list[Union["A", str]], added in 6.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.
"fixed_dictionaries()" now varies the iteration order of the dicts it generates, rather than always placing the required keys first, to help find bugs
"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.
The "--hypothesis-show-statistics" report now accounts for the "Phase.explain" phase separately, rather than including its runtime and test cases in t
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.
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 (4179).
This patch dramatically improves the performance of "from_type()" on hierarchies of abstract classes whose subclasses refer back to the base class (di
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.
This patch dramatically improves the performance of ~hypothesis.strategies.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 (4729).
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 sm
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.
This patch fixes a bug where "decimals()" with the "places" argument could generate values outside the "min_value" and "max_value" bounds, when those
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.
This patch fixes a bug where ~hypothesis.strategies.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 (4651).
This patch improves the performance of stateful testing for state machines with a large number of rules (issue #4465).
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.
This patch improves the performance of stateful testing for state machines with a large number of rules (4465).
This patch fixes a bug where we emitted incorrect git patch files when one file did not have a trailing newline (issue #4744).
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.
This patch fixes a bug where we emitted incorrect git patch files when one file did not have a trailing newline (4744).
"event()"'s "payload" is now typed as accepting "Any", matching its runtime behavior of accepting any string-coercible object.
"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.
|event|'s payload is now typed as accepting |Any|, matching its runtime behavior of accepting any string-coercible object.
When Hypothesis detects that your data generation is flaky and raises "FlakyStrategyDefinition", the error message now describes *what* differed betwe
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.
This patch adds support for recursive forward references in "from_type()", such as "A = list[Union["A", str]]" (issue #4542). Previously, such recursi
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.
This patch adds support for resolving forward references in |st.from_type| (4542):
# this now works
A = list[Union["A", str]]
st.from_type(A).example()
# this also now works
s = st.from_type(list["B"])
@dataclass
class B:
v: int
s.example()
Previously, these would raise an error. Now, Hypothesis automatically resolves the forward reference by looking it up in the caller's namespace.
This patch renames our source code directory from "hypothesis-python" to "hypothesis", and changes our canonical scheme for git tags from "hypothesis-
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.
This release substantially improves our internal distribution for generating integers. This release has the most visible effect on "integers()", but m
This release substantially improves our internal distribution for generating integers. This release has the most visible effect on "integers()", but may incidentally improve other strategies which draw integers internally.
Our integers distribution had two problems. First, it had jagged discontinuities at certain values where we switched sampling approaches. Second, it used a different distribution for bounded and unbounded ranges, which resulted in "st.integers()" and "st.integers(-264, 264)" producing very different distributions despite being semantically similar.
We now use a smooth distribution for both "st.integers()" and "st.integers(a, b)", which fixes both of these issues. This should substantially improve our testing power in certain cases.
The only way this release should be user-visible is that it finds more bugs! If this release is user-visible in other ways - for example, because it is slower, or produces a worse distribution in some cases - please open an issue.
The canonical version of these notes (with links) is on readthedocs.
This release drops support for end-of-life Django 4.2.
This release drops support for end-of-life Django 4.2.
The canonical version of these notes (with links) is on readthedocs.
This patch improves our type hints for ".filter()" to work with "typing.TypeGuard". For example:
This patch improves our type hints for ".filter()" to work with "typing.TypeGuard". For example:
from typing import TypeGuard
from hypothesis import strategies as st
def is_str(x: object) -> TypeGuard[str]: return isinstance(x, str)
s = st.from_type(object).filter(is_str)
reveal_type(s)
The canonical version of these notes (with links) is on readthedocs.
This patch improves our type hints for |.filter| to work with |TypeGuard|. For example:
from typing import TypeGuard
from hypothesis import strategies as st
def is_str(x: object) -> TypeGuard[str]:
return isinstance(x, str)
s = st.from_type(object).filter(is_str)
# previously: SearchStrategy[object]
# now: SearchStrategy[str]
reveal_type(s)
This patch adds a shrinking pass that tries natural text transformations - unicode decomposition (NFD/NFKD) and case mapping - on individual character
This patch adds a shrinking pass that tries natural text transformations - unicode decomposition (NFD/NFKD) and case mapping - on individual characters in string choices. Failures involving e.g. ""À" != "À".lower()" will now reliably shrink to ""A"" rather than sometimes getting stuck on the high-codepoint accented form (issue #4725).
The canonical version of these notes (with links) is on readthedocs.
This patch improves the "Phase.explain" phase so that simple cases like "assert n1 == n2" no longer get a misleading "# or any other generated value"
This patch improves the "Phase.explain" phase so that simple cases like "assert n1 == n2" no longer get a misleading "# or any other generated value" comment (issue #4715). Before falling back to random sampling, we now also try borrowing values from each other arg slice with matching shape.
The canonical version of these notes (with links) is on readthedocs.
This patch fixes a rare internal error during "Phase.explain" introduced in version 6.149.0 for certain strategies (issue #4708).
This patch fixes a rare internal error during "Phase.explain" introduced in version 6.149.0 for certain strategies (issue #4708).
The canonical version of these notes (with links) is on readthedocs.
This patch fixes a rare internal error during |Phase.explain| introduced in 6.149.0 for certain strategies (4708).
The "hypothesis-urandom" backend now reads from "/dev/urandom" with buffering disabled, which improves the control of those hooking "/dev/urandom" to
The "hypothesis-urandom" backend now reads from "/dev/urandom" with buffering disabled, which improves the control of those hooking "/dev/urandom" to change or read Hypothesis's random decisions.
The canonical version of these notes (with links) is on readthedocs.
This release further improves printing of generated values, building on the changes in version 6.151.11.
This release further improves printing of generated values, building on the changes in version 6.151.11.
Principle changes:
In many cases where we would have printed a complex expression producing a value, we now print the repr (or a pretty-printed version of it).
Additionally, in some cases where we would print a complex expression that involved a lambda, we are now able to simplify that expression into a more readable one.
The canonical version of these notes (with links) is on readthedocs.
Improve some internal type hints.
Improve some internal type hints.
The canonical version of these notes (with links) is on readthedocs.
Hypothesis generally recommends that the ".hypothesis" directory not be checked into version control. As a result, Hypothesis now automatically create
Hypothesis generally recommends that the ".hypothesis" directory not be checked into version control. As a result, Hypothesis now automatically creates a ".gitignore" with "*" in the ".hypothesis" directory, which excludes it from being tracked by git.
If you do want to check ".hypothesis" into git, you can remove the ".gitignore" file. Hypothesis will not re-create it unless the entire ".hypothesis" directory is removed.
The canonical version of these notes (with links) is on readthedocs.
This patch fixes our "from_regex()" type annotations so that "from_regex(..., alphabet=None)" is accepted.
This patch fixes our "from_regex()" type annotations so that "from_regex(..., alphabet=None)" is accepted.
This patch also adds unicode line breaks and thai combining vowels to our list of constant strings to upweight at runtime.
The canonical version of these notes (with links) is on readthedocs.
This patch fixes our |st.from_regex| type annotations so that from_regex(..., alphabet=None) is accepted.
This patch also adds unicode line breaks and thai combining vowels to our list of constant strings to upweight at runtime.
This patch removes some newly unnecessary "# type: ignore" comments.
This patch removes some newly unnecessary "# type: ignore" comments.
The canonical version of these notes (with links) is on readthedocs.
This release improves "Phase.explain" output by excluding pytest- related syrupy files as a possible source of variation.
This release improves "Phase.explain" output by excluding pytest- related syrupy files as a possible source of variation.
The canonical version of these notes (with links) is on readthedocs.
This release improves |Phase.explain| output by excluding pytest-related syrupy files as a possible source of variation.
This patch improves printing of primitive values generated from complex strategies, particularly for "from_regex()". Previously, these would often be
This patch improves printing of primitive values generated from complex strategies, particularly for "from_regex()". Previously, these would often be printed as function calls desctribing how to construct them. Now they will always be printed as a literal value.
The canonical version of these notes (with links) is on readthedocs.
This patch improves printing of primitive values generated from complex strategies, particularly for ~hypothesis.strategies.from_regex. Previously, these would often be printed as function calls desctribing how to construct them. Now they will always be printed as a literal value.
When shrinking takes more than five minutes, Hypothesis now prints the "@seed" decorator alongside the slow-shrinking warning so you can reproduce the
When shrinking takes more than five minutes, Hypothesis now prints the "@seed" decorator alongside the slow-shrinking warning so you can reproduce the failure.
Thanks to Ian Hunt-Isaak for this contribution!
The canonical version of these notes (with links) is on readthedocs.
*The canonical version of these notes (with links) is on readthedocs.*
Remove some old unused code.
The canonical version of these notes (with links) is on readthedocs.
This patch fixes a crash when "sys.modules" contains unhashable values, such as "SimpleNamespace" objects (issue #4660).
This patch fixes a crash when "sys.modules" contains unhashable values, such as "SimpleNamespace" objects (issue #4660).
The canonical version of these notes (with links) is on readthedocs.
This patch fixes a crash when sys.modules contains unhashable values, such as ~types.SimpleNamespace objects (4660).
This patch updates our vendored list of top-level domains, which is used by the provisional "domains()" strategy.
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.
This patch updates our vendored list of top-level domains, which is used by the provisional ~hypothesis.provisional.domains strategy.
This patch fixes several duplicate word typos in comments and documentation.
This patch fixes several duplicate word typos in comments and documentation.
The canonical version of these notes (with links) is on readthedocs.
This patch fixes several duplicate word typos in comments and documentation.
This patch teaches our pytest plugin to :ref: find interesting constants when pytest is collecting tests, to avoid arbitrarily attributing the latency
This patch teaches our pytest plugin to find interesting constants when pytest is collecting tests, to avoid arbitrarily attributing the latency to whichever test function happened to be executed first (issue #4627).
[The canonical version of these notes (with links) is on readthedocs.](https://hypothesis.readthedocs.io/en/latest/changelog.html#v6-151-5)
This patch adjusts how we compute the stopping threshold introduced in version 6.151.3, while still maintaining 99% confidence that <1% of test cases
This patch adjusts how we compute the stopping threshold introduced in version 6.151.3, while still maintaining 99% confidence that <1% of test cases pass.
The canonical version of these notes (with links) is on readthedocs.
This patch adjusts how we compute the stopping threshold introduced in 6.151.3, while still maintaining 99% confidence that <1% of test cases pass.
This patch makes Hypothesis more tolerant of slow-to-satisfy "assume()" calls. Previously, Hypothesis would give up after "max_examples * 10" attempts
This patch makes Hypothesis more tolerant of slow-to-satisfy "assume()" calls. Previously, Hypothesis would give up after "max_examples * 10" attempts; now it uses a statistical test to stop only when 99% confident that <1% of examples would pass (issue #4623).
Thanks to @ajdavis for this improvement!
The canonical version of these notes (with links) is on readthedocs.
Format our code with the latest version of black.
Format our code with the latest version of black.
The canonical version of these notes (with links) is on readthedocs.
Improve internal categorization of test cases when an alternative backend raises "BackendCannotProceed".
Improve internal categorization of test cases when an alternative backend raises "BackendCannotProceed".
The canonical version of these notes (with links) is on readthedocs.
Improve internal categorization of test cases when an alternative backend raises |BackendCannotProceed|.
Add 2025.12 to the list of recognized Array API versions in "hypothesis.extra.array_api".
Add 2025.12 to the list of recognized Array API versions in "hypothesis.extra.array_api".
The canonical version of these notes (with links) is on readthedocs.
Add 2025.12 to the list of recognized Array API versions in hypothesis.extra.array_api.
Hypothesis now generates powers of 2 more often when using "integers()".
Hypothesis now generates powers of 2 more often when using "integers()".
The canonical version of these notes (with links) is on readthedocs.
Hypothesis now generates powers of 2 more often when using |st.integers|.
One column per quarter.