Hypothesis

Latest version: v6.99.13

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

Scan your dependencies

Page 165 of 194

3.36.1

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

This is a yak shaving release, mostly concerned with our own tests.

While :func:`~python:inspect.getfullargspec` was documented as deprecated
in Python 3.5, it never actually emitted a warning. Our code to silence
this (nonexistent) warning has therefore been removed.

We now run our tests with ``DeprecationWarning`` as an error, and made some
minor changes to our own tests as a result. This required similar upstream
updates to :pypi:`coverage` and :pypi:`execnet` (a test-time dependency via
:pypi:`pytest-xdist`).

There is no user-visible change in Hypothesis itself, but we encourage you
to consider enabling deprecations as errors in your own tests.

3.36.0

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

This release adds a setting to the public API, and does some internal cleanup:

- The :attr:`~hypothesis.settings.derandomize` setting is now documented (:issue:`890`)
- Removed - and disallowed - all 'bare excepts' in Hypothesis (:issue:`953`)
- Documented the ``strict`` setting as deprecated, and
updated the build so our docs always match deprecations in the code.

3.35.0

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

This minor release supports constraining :func:`~hypothesis.strategies.uuids`
to generate a particular version of :class:`~python:uuid.UUID` (:issue:`721`).

Thanks to Dion Misic for this feature.

3.34.1

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

This patch updates the documentation to suggest
:func:`builds(callable) <hypothesis.strategies.builds>` instead of
:func:`just(callable()) <hypothesis.strategies.just>`.

3.34.0

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

Hypothesis now emits deprecation warnings if you apply
:func:`given <hypothesis.given>` more than once to a target.

Applying :func:`given <hypothesis.given>` repeatedly wraps the target multiple
times. Each wrapper will search the space of of possible parameters separately.
This is equivalent but will be much more inefficient than doing it with a
single call to :func:`given <hypothesis.given>`.

For example, instead of
``given(booleans()) given(integers())``, you could write
``given(booleans(), integers())``

3.33.1

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

This is a bugfix release:

- :func:`~hypothesis.strategies.builds` would try to infer a strategy for
required positional arguments of the target from type hints, even if they
had been given to :func:`~hypothesis.strategies.builds` as positional
arguments (:issue:`946`). Now it only infers missing required arguments.
- An internal introspection function wrongly reported ``self`` as a required
argument for bound methods, which might also have affected
:func:`~hypothesis.strategies.builds`. Now it knows better.

Page 165 of 194

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.