Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
151: Scheduled weekly dependency update for week 35 r=mithrandi
## Updates
Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.
<table align="center">
<tr>
<td><b>hyperlink</b></td>
<td align="center">17.3.0</td>
<td align="center">»</td>
<td align="center">17.3.1</td>
<td>
<a href="https://pypi.python.org/pypi/hyperlink">PyPI</a> | <a href="https://pyup.io/changelogs/hyperlink/">Changelog</a> | <a href="https://github.com/python-hyper/hyperlink">Repo</a>
</td>
<tr>
<td><b>hypothesis</b></td>
<td align="center">3.18.0</td>
<td align="center">»</td>
<td align="center">3.22.0</td>
<td>
<a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a>
</td>
<tr>
<td><b>pyasn1-modules</b></td>
<td align="center">0.0.11</td>
<td align="center">»</td>
<td align="center">0.1.1</td>
<td>
<a href="https://pypi.python.org/pypi/pyasn1-modules">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1-modules/">Changelog</a> | <a href="https://github.com/etingof/pyasn1-modules">Repo</a>
</td>
<tr>
<td><b>pyasn1</b></td>
<td align="center">0.3.2</td>
<td align="center">»</td>
<td align="center">0.3.3</td>
<td>
<a href="https://pypi.python.org/pypi/pyasn1">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1/">Changelog</a> | <a href="https://github.com/etingof/pyasn1">Repo</a>
</td>
</tr>
</table>
## Changelogs
### hypothesis 3.18.0 -> 3.22.0
>### 3.22.0
>-------------------
>This release provides what should be a substantial performance improvement to
>numpy arrays generated using :ref:`provided numpy support <hypothesis-numpy>`,
>and adds a new ``fill_value`` argument to :func:`~hypothesis.extra.numpy.arrays`
>to control this behaviour.
>This work was funded by `Stripe <https://stripe.com/>`_.
>-------------------
>### 3.21.3
>-------------------
>This release fixes some extremely specific circumstances that probably have
>never occurred in the wild where users of
>:func:`~hypothesis.searchstrategy.deferred` might have seen a RuntimeError from
>too much recursion, usually in cases where no valid example could have been
>generated anyway.
>-------------------
>### 3.21.2
>-------------------
>This release fixes some minor bugs in argument validation:
> * :ref:`hypothesis.extra.numpy <hypothesis-numpy>` dtype strategies would raise an internal error
> instead of an InvalidArgument exception when passed an invalid
> endianness specification.
> * :func:`~hypothesis.strategies.fractions` would raise an internal error instead of an InvalidArgument
> if passed ``float("nan")`` as one of its bounds.
> * The error message for passing ``float("nan")`` as a bound to various
> strategies has been improved.
> * Various bound arguments will now raise InvalidArgument in cases where
> they would previously have raised an internal TypeError or
> ValueError from the relevant conversion function.
> * :func:`~hypothesis.strategies.streaming` would not have emitted a
> deprecation warning when called with an invalid argument.
>-------------------
>### 3.21.1
>-------------------
>This release fixes a bug where test failures that were the result of
>an example would print an extra stack trace before re-raising the
>exception.
>-------------------
>### 3.21.0
>-------------------
>This release deprecates Hypothesis's strict mode, which turned Hypothesis's
>deprecation warnings into errors. Similar functionality can be achieved
>by using :func:`simplefilter('error', HypothesisDeprecationWarning) <python:warnings.simplefilter>`.
>-------------------
>### 3.20.0
>-------------------
>This release renames the relevant arguments on the
>:func:`~hypothesis.strategies.datetimes`, :func:`~hypothesis.strategies.dates`,
>:func:`~hypothesis.strategies.times`, and :func:`~hypothesis.strategies.timedeltas`
>strategies to ``min_value`` and ``max_value``, to make them consistent with the
>other strategies in the module.
>The old argument names are still supported but will emit a deprecation warning
>when used explicitly as keyword arguments. Arguments passed positionally will
>go to the new argument names and are not deprecated.
>-------------------
>### 3.19.3
>-------------------
>This release provides a major overhaul to the internals of how Hypothesis
>handles shrinking.
>This should mostly be visible in terms of getting better examples for tests
>which make heavy use of :func:`~hypothesis.strategies.composite`,
>:ref:`data <interactive-draw>` or :ref:`flatmap <flatmap>` where the data
>drawn depends a lot on previous choices, especially where size parameters are
>affected. Previously Hypothesis would have struggled to reliably produce
>good examples here. Now it should do much better. Performance should also be
>better for examples with a non-zero ``min_size``.
>You may see slight changes to example generation (e.g. improved example
>diversity) as a result of related changes to internals, but they are unlikely
>to be significant enough to notice.
>-------------------
>### 3.19.2
>-------------------
>This release fixes two bugs in ``hypothesis.extra.numpy``:
>* :func:`~hypothesis.extra.numpy.unicode_string_dtypes` didn't work at all due
> to an incorrect dtype specifier. Now it does.
>* Various impossible conditions would have been accepted but would error when
> they fail to produced any example. Now they raise an explicit InvalidArgument
> error.
>-------------------
>### 3.19.1
>-------------------
>This is a bugfix release for :issue:`739`, where bounds for
>:func:`~hypothesis.strategies.fractions` or floating-point
>:func:`~hypothesis.strategies.decimals` were not properly converted to
>integers before passing them to the integers strategy.
>This excluded some values that should have been possible, and could
>trigger internal errors if the bounds lay between adjacent integers.
>You can now bound :func:`~hypothesis.strategies.fractions` with two
>arbitrarily close fractions.
>It is now an explicit error to supply a min_value, max_value, and
>max_denominator to :func:`~hypothesis.strategies.fractions` where the value
>bounds do not include a fraction with denominator at most max_denominator.
>-------------------
>### 3.19.0
>-------------------
>This release adds the :func:`~hypothesis.strategies.from_regex` strategy,
>which generates strings that contain a match of a regular expression.
>Thanks to Maxim Kulkin for creating the
>`hypothesis-regex <https://github.com/maximkulkin/hypothesis-regex>`_
>package and then helping to upstream it! (:issue:`662`)
>-------------------
>### 3.18.5
>-------------------
>This is a bugfix release for :func:`~hypothesis.strategies.integers`.
>Previously the strategy would hit an internal assertion if passed non-integer
>bounds for ``min_value`` and ``max_value`` that had no integers between them.
>The strategy now raises InvalidArgument instead.
>-------------------
>### 3.18.4
>-------------------
>Release to fix a bug where mocks can be used as test runners under certain
>conditions. Specifically, if a mock is injected into a test via pytest
>fixtures or patch decorators, and that mock is the first argument in the
>list, hypothesis will think it represents self and turns the mock
>into a test runner. If this happens, the affected test always passes
>because the mock is executed instead of the test body. Sometimes, it
>will also fail health checks.
>Fixes :issue:`491` and a section of :issue:`198`.
>Thanks to Ben Peterson for this bug fix.
>-------------------
>### 3.18.3
>-------------------
>This release should improve the performance of some tests which
>experienced a slow down as a result of the 3.13.0 release.
>Tests most likely to benefit from this are ones that make extensive
>use of `min_size` parameters, but others may see some improvement
>as well.
>-------------------
>### 3.18.2
>-------------------
>This release fixes a bug introduced in 3.18.0. If the arguments
>``whitelist_characters`` and ``blacklist_characters`` to
>:func:`~hypothesis.strategies.characters` both contained elements, then an
>``InvalidArgument`` exception would be raised.
>Thanks to Zac Hatfield-Dodds for reporting and fixing this.
>-------------------
>### 3.18.1
>-------------------
>This is a bug fix release to fix :issue:`780`, where
>:func:`~hypothesis.strategies.sets` and similar would trigger health check
>errors if their element strategy could only produce one element (e.g.
>if it was :func:`~hypothesis.strategies.just`).
>-------------------
That's it for now!
Happy merging! 🤖- Loading branch information
