Update hypothesis to 3.44.9

[pyup-bot]

There's a new version of hypothesis available.
You are currently using 3.42.2. I have updated it to 3.44.9

These links might come in handy: PyPI | Changelog | Repo

Changelog

3.44.9

---

This patch blacklists null characters ('\x00') in automatically created
strategies for Django :obj:~django:django.db.models.CharField and
:obj:~django:django.db.models.TextField, due to a database issue which
was recently fixed upstream <https://code.djangoproject.com/ticket/28201>_
(Hypothesis :issue:1045).

---

3.44.8

---

This release makes the Hypothesis shrinker slightly less greedy in order to
avoid local minima - when it gets stuck, it makes a small attempt to search
around the final example it would previously have returned to find a new
starting point to shrink from. This should improve example quality in some
cases, especially ones where the test data has dependencies among parts of it
that make it difficult for Hypothesis to proceed.

---

3.44.7

---

This release adds support for Django 2 <https://www.djangoproject.com/weblog/2017/dec/02/django-20-released/>_ in
the hypothesis-django extra.

This release drops support for Django 1.10, as it is no longer supported by
the Django team.

---

3.44.6

---

This release speeds up test case reduction in many examples by being better at
detecting large shrinks it can use to discard redundant parts of its input.
This will be particularly noticeable in examples that make use of filtering
and for some integer ranges.

---

3.44.5

---

Happy new year!

This is a no-op release that updates the year range on all of
the copyright headers in our source to include 2018.

---

3.44.4

---

This release fixes :issue:1044, which slowed tests by up to 6%
due to broken caching.

---

3.44.3

---

This release improves the shrinker in cases where examples drawn earlier can
affect how much data is drawn later (e.g. when you draw a length parameter in
a composite and then draw that many elements). Examples found in cases like
this should now be much closer to minimal.

---

3.44.2

---

This is a pure refactoring release which changes how Hypothesis manages its
set of examples internally. It should have no externally visible effects.

---

3.44.1

---

This release fixes :issue:997, in which under some circumstances the body of
tests run under Hypothesis would not show up when run under coverage even
though the tests were run and the code they called outside of the test file
would show up normally.

---

3.44.0

---

This release adds a new feature: The :ref:reproduce_failure <reproduce_failure>,
designed to make it easy to use Hypothesis's binary format for examples to
reproduce a problem locally without having to share your example database
between machines.

This also changes when seeds are printed:

• They will no longer be printed for
  normal falsifying examples, as there are now adequate ways of reproducing those
  for all cases, so it just contributes noise.
• They will once again be printed when reusing examples from the database, as
  health check failures should now be more reliable in this scenario so it will
  almost always work in this case.

This work was funded by Smarkets <https://smarkets.com/>_.

---

3.43.1

---

This release fixes a bug with Hypothesis's database management - examples that
were found in the course of shrinking were saved in a way that indicated that
they had distinct causes, and so they would all be retried on the start of the
next test. The intended behaviour, which is now what is implemented, is that
only a bounded subset of these examples would be retried.

---

3.43.0

---

:exc:~hypothesis.errors.HypothesisDeprecationWarning now inherits from
:exc:python:FutureWarning instead of :exc:python:DeprecationWarning,
as recommended by :pep:565 for user-facing warnings (:issue:618).
If you have not changed the default warnings settings, you will now see
each distinct :exc:~hypothesis.errors.HypothesisDeprecationWarning
instead of only the first.

---

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

[pyup-bot]

Closing this in favor of #136