Workflow

Hypothesis

Latest version: v6.100.1

Safety actively analyzes 619566 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 154 of 195

3.52.1

Not secure
-------------------

This release improves the behaviour of :doc:`stateful testing <stateful>`
in two ways:

* Previously some runs would run no steps (:issue:`376`). This should no longer
happen.
* RuleBasedStateMachine tests which used bundles extensively would often shrink
terribly. This should now be significantly improved, though there is likely
a lot more room for improvement.

This release also involves a low level change to how ranges of integers are
handles which may result in other improvements to shrink quality in some cases.

3.52.0

Not secure
-------------------

This release deprecates use of :func:`settings(...) <hypothesis.settings>`
as a decorator, on functions or methods that are not also decorated with
:func:`given <hypothesis.given>`. You can still apply these decorators
in any order, though you should only do so once each.

Applying :func:`given <hypothesis.given>` twice was already deprecated, and
applying :func:`settings(...) <hypothesis.settings>` twice is deprecated in
this release and will become an error in a future version. Neither could ever
be used twice to good effect.

Using :func:`settings(...) <hypothesis.settings>` as the sole decorator on
a test is completely pointless, so this common usage error will become an
error in a future version of Hypothesis.

3.51.0

Not secure
-------------------

This release deprecates the ``average_size`` argument to
:func:`~hypothesis.strategies.lists` and other collection strategies.
You should simply delete it wherever it was used in your tests, as it
no longer has any effect.

In early versions of Hypothesis, the ``average_size`` argument was treated
as a hint about the distribution of examples from a strategy. Subsequent
improvements to the conceptual model and the engine for generating and
shrinking examples mean it is more effective to simply describe what
constitutes a valid example, and let our internals handle the distribution.

3.50.3

Not secure
-------------------

This patch contains some internal refactoring so that we can run
with warnings as errors in CI.

3.50.2

Not secure
-------------------

This has no user-visible changes except one slight formatting change to one docstring, to avoid a deprecation warning.

3.50.1

Not secure
-------------------

This patch fixes an internal error introduced in :ref:`3.48.0 <v3.48.0>`, where a check
for the Django test runner would expose import-time errors in Django
configuration (:issue:`1167`).

Page 154 of 195

Links

Releases

Has known vulnerabilities

Previous Next

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.