Merge #184

184: Scheduled weekly dependency update for week 09 r=mithrandi a=pyup-bot




## 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.1</td>
<td align="center">&raquo;</td>
<td align="center">18.0.0</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.44.16</td>
<td align="center">&raquo;</td>
<td align="center">3.48.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>
</table>



## Changelogs


### hypothesis 3.44.16 -> 3.48.0

>### 3.48.0

>-------------------

>This release improves some &quot;unhappy paths&quot; when using Hypothesis
>with the standard library :mod:`python:unittest` module:

>- Applying :func:`given &lt;hypothesis.given&gt;` to a non-test method which is
>  overridden from :class:`python:unittest.TestCase`, such as ``setUp``,
>  raises :attr:`a new health check &lt;hypothesis.settings.not_a_test_method&gt;`.
>  (:issue:`991`)
>- Using :meth:`~python:unittest.TestCase.subTest` within a test decorated
>  with :func:`given &lt;hypothesis.given&gt;` would leak intermediate results
>  when tests were run under the :mod:`python:unittest` test runner.
>  Individual reporting of failing subtests is now disabled during a test
>  using :func:`given &lt;hypothesis.given&gt;`.  (:issue:`1071`)
>- :func:`given &lt;hypothesis.given&gt;` is still not a class decorator, but the
>  error message if you try using it on a class has been improved.

>As a related improvement, using :class:`django:django.test.TestCase` with
>:func:`given &lt;hypothesis.given&gt;` instead of
>:class:`hypothesis.extra.django.TestCase` raises an explicit error instead
>of running all examples in a single database transaction.

>-------------------


>### 3.47.0

>-------------------

>:obj:`~hypothesis.settings.register_profile` now accepts keyword arguments
>for specific settings, and the parent settings object is now optional.
>Using a ``name`` for a registered profile which is not a string was never
>suggested, but it is now also deprecated and will eventually be an error.

>-------------------


>### 3.46.2

>-------------------

>This release removes an unnecessary branch from the code, and has no user-visible impact.

>-------------------


>### 3.46.1

>-------------------

>This changes only the formatting of our docstrings and should have no user-visible effects.

>-------------------


>### 3.46.0

>-------------------

>:func:`~hypothesis.strategies.characters` has improved docs about
>what arguments are valid, and additional validation logic to raise a
>clear error early (instead of e.g. silently ignoring a bad argument).
>Categories may be specified as the Unicode &#39;general category&#39;
>(eg ``u&#39;Nd&#39;``), or as the &#39;major category&#39; (eg ``[u&#39;N&#39;, u&#39;Lu&#39;]``
>is equivalent to ``[u&#39;Nd&#39;, u&#39;Nl&#39;, u&#39;No&#39;, u&#39;Lu&#39;]``).

>In previous versions, general categories were supported and all other
>input was silently ignored.  Now, major categories are supported in
>addition to general categories (which may change the behaviour of some
>existing code), and all other input is deprecated.

>-------------------


>### 3.45.5

>-------------------

>This patch improves strategy inference in :mod:`hypothesis.extra.django`
>to account for some validators in addition to field type - see
>:issue:`1116` for ongoing work in this space.

>Specifically, if a :class:`~django:django.db.models.CharField` or
>:class:`~django:django.db.models.TextField` has an attached
>:class:`~django:django.core.validators.RegexValidator`, we now use
>:func:`~hypothesis.strategies.from_regex` instead of
>:func:`~hypothesis.strategies.text` as the underlying strategy.
>This allows us to generate examples of the default
>:class:`~django:django.contrib.auth.models.User` model, closing :issue:`1112`.

>-------------------


>### 3.45.4

>-------------------

>This patch improves some internal debugging information, fixes
>a typo in a validation error message, and expands the documentation
>for new contributors.

>-------------------


>### 3.45.3

>-------------------

>This patch may improve example shrinking slightly for some strategies.

>-------------------


>### 3.45.2

>-------------------

>This release makes our docstring style more consistent, thanks to
>:pypi:`flake8-docstrings`.  There are no user-visible changes.

>-------------------


>### 3.45.1

>-------------------

>This fixes an indentation issue in docstrings for
>:func:`~hypothesis.strategies.datetimes`, :func:`~hypothesis.strategies.dates`,
>:func:`~hypothesis.strategies.times`, and
>:func:`~hypothesis.strategies.timedeltas`.

>-------------------


>### 3.45.0

>-------------------

>This release fixes :func:`~hypothesis.strategies.builds` so that ``target``
>can be used as a keyword argument for passing values to the target. The target
>itself can still be specified as a keyword argument, but that behavior is now
>deprecated. The target should be provided as the first positional argument.

>--------------------


>### 3.44.26

>--------------------

>This release fixes some formatting issues in the Hypothesis source code.
>It should have no externally visible effects.

>--------------------


>### 3.44.25

>--------------------

>This release changes the way in which Hypothesis tries to shrink the size of
>examples. It probably won&#39;t have much impact, but might make shrinking faster
>in some cases. It is unlikely but not impossible that it will change the
>resulting examples.

>--------------------


>### 3.44.24

>--------------------

>This release fixes dependency information when installing Hypothesis
>from a binary &quot;wheel&quot; distribution.

>- The ``install_requires`` for :pypi:`enum34` is resolved at install
>  time, rather than at build time (with potentially different results).
>- Django has fixed their ``python_requires`` for versions 2.0.0 onward,
>  simplifying Python2-compatible constraints for downstream projects.

>--------------------


>### 3.44.23

>--------------------

>This release improves shrinking in a class of pathological examples that you
>are probably never hitting in practice. If you *are* hitting them in practice
>this should be a significant speed up in shrinking. If you are not, you are
>very unlikely to notice any difference. You might see a slight slow down and/or
>slightly better falsifying examples.

>--------------------


>### 3.44.22

>--------------------

>This release fixes a dependency problem.  It was possible to install
>Hypothesis with an old version of :pypi:`attrs`, which would throw a
>``TypeError`` as soon as you tried to import hypothesis.  Specifically, you
>need attrs 16.0.0 or newer.

>Hypothesis will now require the correct version of attrs when installing.

>--------------------


>### 3.44.21

>--------------------

>This change adds some additional structural information that Hypothesis will
>use to guide its search.

>You mostly shouldn&#39;t see much difference from this. The two most likely effects
>you would notice are:

>1. Hypothesis stores slightly more examples in its database for passing tests.
>2. Hypothesis *may* find new bugs that it was previously missing, but it
>   probably won&#39;t (this is a basic implementation of the feature that is
>   intended to support future work. Although it is useful on its own, it&#39;s not
>   *very* useful on its own).

>--------------------


>### 3.44.20

>--------------------

>This is a small refactoring release that changes how Hypothesis tracks some
>information about the boundary of examples in its internal representation.

>You are unlikely to see much difference in behaviour, but memory usage and
>run time may both go down slightly during normal test execution, and when
>failing Hypothesis might print its failing example slightly sooner.

>--------------------


>### 3.44.19

>--------------------

>This changes how we compute the default ``average_size`` for all collection
>strategies. Previously setting a ``max_size`` without setting an
>``average_size`` would have the seemingly paradoxical effect of making data
>generation *slower*, because it would raise the average size from its default.
>Now setting ``max_size`` will either leave the default unchanged or lower it
>from its default.

>If you are currently experiencing this problem, this may make your tests
>substantially faster. If you are not, this will likely have no effect on you.

>--------------------


>### 3.44.18

>--------------------

>This is a small refactoring release that changes how Hypothesis detects when
>the structure of data generation depends on earlier values generated (e.g. when
>using :ref:`flatmap &lt;flatmap&gt;` or :func:`~hypothesis.strategies.composite`).
>It should not have any observable effect on behaviour.

>--------------------


>### 3.44.17

>--------------------

>This release fixes a typo in internal documentation, and has no user-visible impact.

>--------------------









That's it for now!

Happy merging! 🤖

requirements.txt

@@ -18,8 +18,8 @@ epsilon==0.7.1
 extras==1.0.0
 fixtures==3.0.0
 fusion-util==1.3.0
-hyperlink==17.3.1
-hypothesis==3.44.16
+hyperlink==18.0.0
+hypothesis==3.48.0
 idna==2.6
 incremental==17.5.0
 ipaddress==1.0.19