Log message:
py-hypothesis: updated to 3.59.0

3.59.0:
This release adds the :func:~hypothesis.strategies.emails strategy, which \ 
generates unicode strings representing an email address.

3.58.1:
This improves the shrinker. It can now reorder examples: 3 1 2 becomes 1 2 3.

3.58.0:
This adds a new extra :py:func:~hypothesis.extra.dateutil.timezones strategy \ 
that generates dateutil timezones.
Depends on :pypi:python-dateutil.

Log message:
py-hypothesis: updated to 3.57.0

3.57.0:
Using an unordered collection with the :func:~hypothesis.strategies.permutations \ 
strategy has been deprecated because the order in which e.g. a set shrinks is \ 
arbitrary. This may cause different results between runs.

3.56.10:
This release makes :obj:~hypothesis.settings.define_setting a private method, \ 
which has the effect of hiding it from the documentation.

3.56.9:
This is another release with no functionality changes as part of changes to \ 
Hypothesis's new release tagging scheme.

3.56.8:
This is a release with no functionality changes that moves Hypothesis over to a \ 
new release tagging scheme.

3.56.7:
This release provides a performance improvement for most tests, but in \ 
particular users of sampled_from who don't have numpy installed should see a \ 
significant performance improvement.

3.56.6:
This patch contains further internal work to support Mypy. There are no \ 
user-visible changes... yet.

Log message:
py-hypothesis: updated to 3.56.5

3.56.5:
This patch contains some internal refactoring to run :pypi:mypy in CI. There are \ 
no user-visible changes.

3.56.4:
This release involves some very minor internal clean up and should have no user \ 
visible effect at all.

3.56.3:
This release fixes a problem introduced in :ref:3.56.0 <v3.56.0> where \ 
setting the hypothesis home directory (through currently undocumented means) \ 
would no longer result in the default database location living in the new home \ 
directory.

3.56.2:
This release fixes a problem introduced in :ref:3.56.0 <v3.56.0> where \ 
setting :obj:~hypothesis.settings.max_examples to 1 would result in tests \ 
failing with Unsatisfiable. This problem could also occur in other harder to \ 
trigger circumstances (e.g. by setting it to a low value, having a hard to \ 
satisfy assumption, and disabling health checks).

3.56.1:
This release fixes a problem that was introduced in :ref:3.56.0 <v3.56.0>: \ 
Use of the :envvar:HYPOTHESIS_VERBOSITY_LEVEL environment variable was, rather \ 
than deprecated, actually broken due to being read before various setup the \ 
deprecation path needed was done. It now works correctly (and emits a \ 
deprecation warning).

3.56.0:
This release deprecates several redundant or internally oriented \ 
:class:~hypothesis.settings, working towards an orthogonal set of configuration \ 
options that are widely useful without requiring any knowledge of our internals

Log message:
py-hypothesis: updated to 3.55.0

3.55.0:
This release includes several improvements to the handling of the \ 
:obj:~hypothesis.settings.database setting.

The :obj:~hypothesis.settings.database_file setting was a historical artefact, \ 
and you should just use :obj:~hypothesis.settings.database directly.
The :envvar:HYPOTHESIS_DATABASE_FILE environment variable is deprecated, in \ 
favor of :meth:~hypothesis.settings.load_profile and the \ 
:obj:~hypothesis.settings.database setting.
If you have not configured the example database at all and the default location \ 
is not usable (due to e.g. permissions issues), Hypothesis will fall back to an \ 
in-memory database. This is not persisted between sessions, but means that the \ 
defaults work on read-only filesystems.

3.54.0:
This release improves the :func:~hypotheses.strategies.complex_numbers strategy, \ 
which now supports min_magnitude and max_magnitude arguments, along with \ 
allow_nan and allow_infinity like for :func:~hypotheses.strategies.floats.

3.53.0:
This release removes support for Django 1.8, which reached end of life on 2018-04-01.

Log message:
py-hypothesis: updated to 3.50.2

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

3.50.1:
This patch fixes an internal error introduced in 3.48.0, where a check for the \ 
Django test runner would expose import-time errors in Django configuration.

3.50.0:
This release improves validation of numeric bounds for some strategies.

Log message:
py-hypothesis: updated to 3.49.1

3.49.1:
This patch fixes our tests for Numpy dtype strategies on big-endian platforms, \ 
where the strategy behaved correctly but the test assumed that the native byte \ 
order was little-endian.

There is no user impact unless you are running our test suite on big-endian \ 
platforms. Thanks to Graham Inggs for reporting :issue:1164.

3.49.0:
This release deprecates passing elements=None to collection strategies, such as \ 
:func:~hypothesis.strategies.lists.

Requiring lists(nothing()) or builds(list) instead of lists() means slightly \ 
more typing, but also improves the consistency and discoverability of our API - \ 
as well as showing how to compose or construct strategies in ways that still \ 
work in more complex situations.

Passing a nonzero max_size to a collection strategy where the elements strategy \ 
contains no values is now deprecated, and will be an error in a future version. \ 
The equivalent with elements=None is already an error.

Log message:
py-hypothesis: updated to 3.48.1

3.48.1:
This patch will minimize examples that would come out non-minimal in previous \ 
versions.

Log message:
py-hypothesis: updated 3.48.0

3.48.0:
This release improves some "unhappy paths" when using Hypothesis with \ 
the standard library :mod:python:unittest module:

* Applying :func:@given <hypothesis.given> to a non-test method which is \ 
overridden from :class:python:unittest.TestCase, such as setUp, raises :attr:a \ 
new health check <hypothesis.settings.not_a_test_method>. (:issue:991)
* Using :meth:~python:unittest.TestCase.subTest within a test decorated with \ 
:func:@given <hypothesis.given> 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 \ 
<hypothesis.given>. (:issue:1071)
* :func:@given <hypothesis.given> 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 <hypothesis.given> instead of \ 
:class:hypothesis.extra.django.TestCase raises an explicit error instead of \ 
running all examples in a single database transaction.

Log message:
py-hypothesis: updated to 3.47.0

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.

Log message:
py-hypothesis: updated to 3.46.0

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 'general category' (eg u'Nd'), or as the 'major category' (eg [u'N', \ 
u'Lu'] is equivalent to [u'Nd', u'Nl', u'No', u'Lu'].

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.