2023-10-04 22:40:59 by Adam Ciarcinski | Files touched by this commit (3) | |
Log message:
py-hypothesis: updated to 6.87.1
6.87.1
Fixes issue 3755, where an internal condition turns out to be reachable after all.
6.87.0
This release deprecates use of assume() and reject() outside of property-based \
tests, because these functions work by raising a special exception (issue 3743). \
It also fixes some type annotations
|
2023-09-18 07:56:32 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-hypothesis: updated to 6.86.1
6.86.1
This patch improves the documentation of @example(...).xfail() by adding a note \
about PEP 614, similar to @example(...).via(), and adds a warning when a \
strategy generates a test case which seems identical to one provided by an \
xfailed example.
6.86.0
This release enables the explain phase by default. We hope it helps you to \
understand why your failing tests have failed!
6.85.1
This patch switches some of our type annotations to use typing.Literal when only \
a few specific values are allowed, such as UUID or IP address versions.
6.85.0
This release deprecates the old whitelist/blacklist arguments to characters(), \
in favor of include/exclude arguments which more clearly describe their effects \
on the set of characters which can be generated.
You can use Hypothesis’ codemods to automatically upgrade to the new argument \
names. In a future version, the old names will start to raise a \
DeprecationWarning.
6.84.3
This patch automatically disables the differing_executors health check for \
methods which are also pytest parametrized tests, because those were mostly \
false alarms.
6.84.2
Building on recent releases, characters() now accepts _any_ codec=, not just \
"utf-8" and "ascii".
This includes standard codecs from the codecs module and their aliases, platform \
specific and user-registered codecs if they are available, and python-specific \
text encodings (but not text transforms or binary transforms).
6.84.1
This patch by Reagan Lee makes st.text(...).filter(str.isidentifier) return an \
efficient custom strategy.
6.84.0
The from_regex() strategy now takes an optional \
alphabet=characters(codec="utf-8") argument for unicode strings, like \
text().
This offers more and more-consistent control over the generated strings, \
removing previously-hard-coded limitations. With fullmatch=False and \
alphabet=characters(), surrogate characters are now possible in leading and \
trailing text as well as the body of the match. Negated character classes such \
as [^A-Z] or \S had a hard-coded exclusion of control characters and surrogate \
characters; now they permit anything in alphabet= consistent with the class, and \
control characters are permitted by default.
|
2023-08-25 13:08:48 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-hypothesis: updated to 6.82.6
6.82.6
This patch enables and fixes many more of ruff‘s lint rules.
6.82.5
Fixes the error message for missing [cli] extra.
6.82.4
This patch ensures that we always close the download connection in \
GitHubArtifactDatabase.
6.82.3
We can now pretty-print combinations of zero enum.Flag values, like SomeFlag(0), \
which has never worked before.
|
2023-08-07 07:23:00 by Adam Ciarcinski | Files touched by this commit (3) | |
Log message:
py-hypothesis: updated to 6.82.2
6.82.2
This patch fixes pretty-printing of combinations of enum.Flag values, which was \
previously an error
|
2023-08-06 09:17:09 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-hypothesis: updated to 6.82.1
6.82.1
Improve shrinking of floats in narrow regions that don’t cross an integer boundary.
|
2023-07-29 17:36:28 by Adam Ciarcinski | Files touched by this commit (2) |
Log message:
py-hypothesis: fix build with Python 3.8
|
2023-07-20 09:59:05 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-hypothesis: updated to 6.82.0
6.81.2
If the HYPOTHESIS_NO_PLUGINS environment variable is set, we’ll avoid loading \
plugins such as the old Pydantic integration or HypoFuzz’ CLI options.
This is probably only useful for our own self-tests, but documented in case it \
might help narrow down any particularly weird bugs in complex environments.
6.81.1
Fixes some lingering issues with inference of recursive types in \
~hypothesis.strategies.from_type.
6.81.0
This release further improves our .patch-file support from version 6.75, \
skipping duplicates, tests which use data() (and don’t support @example()), \
and various broken edge-cases.
Because libCST has released version 1.0 which uses the native parser by default, \
we no longer set the LIBCST_PARSER_TYPE=native environment variable. If you are \
using an older version, you may need to upgrade or set this envvar for yourself.
6.80.1
This patch updates some internal code for selftests. There is no user-visible change.
6.80.0
This release drops support for Python 3.7, which reached end of life on 2023-06-27.
6.79.4
Fixes occasional recursion-limit-exceeded errors when validating deeply nested \
strategies.
6.79.3
This patch updates our vendored list of top-level domains, which is used by the \
provisional domains() strategy.
6.79.2
Improve the type rendered in from_type(), which improves the coverage of Ghostwriter.
6.79.1
We now test against Python 3.12 beta in CI, and this patch fixes some new \
deprecations.
6.79.0
This release changes register_type_strategy() for compatibility with PEP 585: we \
now store only a single strategy or resolver function which is used for both the \
builtin and the typing module version of each type.
If you previously relied on registering separate strategies for e.g. list vs \
typing.List, you may need to use explicit strategies rather than inferring them \
from types.
|
2023-06-16 10:40:28 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-hypothesis: updated to 6.78.3
6.78.3
This release ensures that Ghostwriter does not use the deprecated aliases for \
the collections.abc classes in collections.
6.78.2
This patch improves Ghostwriter’s use of qualified names for re-exported \
functions and classes, and avoids importing useless TypeVars.
6.78.1
This patch updates our vendored list of top-level domains, which is used by the \
provisional domains() strategy.
6.78.0
New input validation for recursive() will raise an error rather than hanging \
indefinitely if passed invalid max_leaves= arguments.
6.77.0
from_type() now handles numpy array types: np.typing.ArrayLike, \
np.typing.NDArray, and parameterized versions including np.ndarray[shape, \
elem_type].
6.76.0
Warn in from_type() if the inferred strategy has no variation (always returning \
default instances). Also handles numpy data types by calling from_dtype() on the \
corresponding dtype, thus ensuring proper variation for these types.
|
2023-05-07 10:35:49 by Thomas Klausner | Files touched by this commit (3) | |
Log message:
py-hypothesis: update to 6.75.2.
6.75.2 - 2023-05-04
Improved the documentation regarding how to use GitHubArtifactDatabase and fixed \
a bug that occurred in repositories with no existing artifacts.
Thanks to Agustín Covarrubias for this contribution.
6.75.1 - 2023-04-30
hypothesis.errors will now raise AttributeError when attempting to access an \
undefined attribute, rather than returning None.
6.75.0 - 2023-04-30
Sick of adding @example()s by hand? Our Pytest plugin now writes .patch files to \
insert them for you, making this workflow easier than ever before.
Note that you’ll need LibCST (via hypothesis[codemods]), and that \
@example().via() requires PEP 614 (Python 3.9 or later).
|
2023-04-30 19:14:48 by Thomas Klausner | Files touched by this commit (2) | |
Log message:
py-hypothesis: update to 6.74.1.
6.74.1 - 2023-04-28
This patch provides better error messages for datetime- and timedelta-related \
invalid dtypes in our Pandas extra (issue #3518). Thanks to Nick Muoh at the \
PyCon Sprints!
6.74.0 - 2023-04-26
This release adds support for nullable pandas dtypes in pandas() (issue #3604). \
Thanks to Cheuk Ting Ho for implementing this at the PyCon sprints!
6.73.1 - 2023-04-27
This patch updates our minimum Numpy version to 1.16, and restores compatibility \
with versions before 1.20, which were broken by a mistake in Hypothesis 6.72.4 \
(issue #3625).
6.73.0 - 2023-04-25
This release upgrades the explain phase (issue #3411).
Following the first failure, Hypothesis will (usually) track which lines of \
code were executed by passing and failing examples, and report where they \
diverged - with some heuristics to drop unhelpful reports. This is an existing \
feature, now upgraded and newly enabled by default.
After shrinking to a minimal failing example, Hypothesis will try to find \
parts of the example – e.g. separate args to @given() – which can vary \
freely without changing the result of that minimal failing example. If the \
automated experiments run without finding a passing variation, we leave a \
comment in the final report:
test_x_divided_by_y(
x=0, # or any other generated value
y=0,
)
Just remember that the lack of an explanation sometimes just means that \
Hypothesis couldn’t efficiently find one, not that no explanation (or simpler \
failing example) exists.
6.72.4 - 2023-04-25
This patch fixes type annotations for the arrays() strategy. Thanks to Francesc \
Elies for pull request #3602.
6.72.3 - 2023-04-25
This patch fixes a bug with from_type() with dict[tuple[int, int], str] (issue \
#3527).
Thanks to Nick Muoh at the PyCon Sprints!
6.72.2 - 2023-04-24
This patch refactors our internals to facilitate an upcoming feature.
6.72.1 - 2023-04-19
This patch fixes some documentation and prepares for future features.
6.72.0 - 2023-04-16
This release deprecates Healthcheck.all(), and adds a codemod to automatically \
replace it with list(Healthcheck) (issue #3596).
6.71.0 - 2023-04-07
This release adds GitHubArtifactDatabase, a new database backend that allows \
developers to access the examples found by a Github Actions CI job. This is \
particularly useful for workflows that involve continuous fuzzing, like \
HypoFuzz.
Thanks to Agustín Covarrubias for this feature!
6.70.2 - 2023-04-03
This patch clarifies the reporting of time spent generating data. A simple \
arithmetic mean of the percentage of time spent can be misleading; reporting the \
actual time spent avoids misunderstandings.
Thanks to Andrea Reina for reporting and fixing issue #3598!
|