Log message:
3.11.1:
This is a minor ergonomics release. Tracebacks shown by pytest no longer include \ 
Hypothesis internals for test functions decorated with @given.

Log message:
Changes 3.11.0:

This is a feature release, adding datetime-related strategies to the core strategies.

extra.pytz.timezones allows you to sample pytz timezones from the Olsen \ 
database. Use directly in a recipe for tz-aware datetimes, or compose with \ 
st.none() to allow a mix of aware and naive output.

The new dates, times, datetimes, and timedeltas strategies in \ 
hypothesis.strategies are all constrained by objects of their type. This means \ 
that you can generate dates bounded by a single day (i.e. a single date), or \ 
datetimes constrained to the microsecond.

times and datetimes take an optional timezones= argument, which defaults to \ 
none() for naive times. You can use our extra strategy based on pytz, or roll \ 
your own timezones strategy with dateutil or even the standard library.

The old dates, times, and datetimes strategies in hypothesis.extra.datetimes are \ 
deprecated in favor of the new core strategies, which are more flexible and have \ 
no dependencies.

Log message:
Changes 3.10.0:
Hypothesis now uses inspect.getfullargspec internally. On Python 2, there are no \ 
visible changes.

On Python 3 @given and @composite now preserve annotations on the decorated \ 
function. Keyword-only arguments are now either handled correctly (e.g. \ 
@composite), or caught in validation instead of silently discarded or raising an \ 
unrelated error later (e.g. @given).

Log message:
3.9.0 - 2017-05-19
This is feature release, expanding the capabilities of the decimals strategy.
* The new (optional) places argument allows you to generate decimals with a \ 
certain number of places (e.g. cents, thousandths, satoshis).
* If allow_infinity is None, setting min_bound no longer excludes positive \ 
infinity and setting max_value no longer excludes negative infinity.
* All of NaN, -Nan, sNaN, and -sNaN may now be drawn if allow_nan is True, or if \ 
allow_nan is None and min_value or max_value is None.
* min_value and max_value may be given as decimal strings, e.g. "1.234".

Log message:
Changes 3.8.5:
Import sqlite3 only if used; minor bugfixes

Log message:
Changes 3.8.3:
Remove pytest version check

Log message:
Updated py-hypothesis to 3.8.2.

3.8.2 - 2017-04-26

This is a code reorganisation release that moves some internal test helpers out \ 
of the main source tree so as to not have changes to them trigger releases in \ 
future.

3.8.1 - 2017-04-26

This is a documentation release. Almost all code examples are now doctests \ 
checked in CI, eliminating stale examples.

3.8.0 - 2017-04-23

This is a feature release, adding the iterables strategy, equivalent to \ 
lists(...).map(iter) but with a much more useful repr. You can use this strategy \ 
to check that code doesn’t accidentally depend on sequence properties such \ 
as indexing support or repeated iteration.

3.7.4 - 2017-04-22

This is a bug fix release for a single bug:

    In 3.7.3, using @example and a pytest fixture in the same test could cause \ 
the test to fail to fill the arguments, and throw a TypeError.

3.7.3 - 2017-04-21

This release should include no user visible changes and is purely a refactoring \ 
release. This modularises the behaviour of the core “given” function, \ 
breaking it up into smaller and more accessible parts, but its actual behaviour \ 
should remain unchanged.

3.7.2 - 2017-04-21

This reverts an undocumented change in 3.7.1 which broke installation on debian \ 
stable: The specifier for the hypothesis[django] extra_requires had introduced a \ 
wild card, which was not supported on the default version of pip.

3.7.1 - 2017-04-21

This is a bug fix and internal improvements release.

    In particular Hypothesis now tracks a tree of where it has already explored. \ 
This allows it to avoid some classes of duplicate examples, and significantly \ 
improves the performance of shrinking failing examples by allowing it to skip \ 
some shrinks that it can determine can’t possibly work.
    Hypothesis will no longer seed the global random arbitrarily unless you have \ 
asked it to using random_module()
    Shrinking would previously have not worked correctly in some special cases \ 
on Python 2, and would have resulted in suboptimal examples.

Log message:
Updated py-hypothesis to 3.7.0.

3.7.0 - 2017-03-20

This is a feature release.

New features:

    Rule based stateful testing now has an @invariant decorator that specifies \ 
methods that are run after init and after every step, allowing you to encode \ 
properties that should be true at all times. Thanks to Tom Prince for this \ 
feature.
    The decimals strategy now supports allow_nan and allow_infinity flags.
    There are significantly more strategies available for numpy, including for \ 
generating arbitrary data types. Thanks to Zac Hatfield Dodds for this feature.
    When using the data() strategy you can now add a label as an argument to \ 
draw(), which will be printed along with the value when an example fails. Thanks \ 
to Peter Inglesby for this feature.

Bug fixes:

    Bug fix: @composite now preserves functions’ docstrings.
    The build is now reproducible and doesn’t depend on the path you build \ 
it from. Thanks to Chris Lamb for this feature.
    numpy strategies for the void data type did not work correctly. Thanks to \ 
Zac Hatfield Dodds for this fix.

There have also been a number of performance optimizations:

    The permutations() strategy is now significantly faster to use for large \ 
lists (the underlying algorithm has gone from O(n^2) to O(n)).
    Shrinking of failing test cases should have got significantly faster in some \ 
circumstances where it was previously struggling for a long time.
    Example generation now involves less indirection, which results in a small \ 
speedup in some cases (small enough that you won’t really notice it except \ 
in pathological cases).

Log message:
Updated py-hypothesis to 3.6.1.

3.6.1 - 2016-12-20

This release fixes a dependency problem and makes some small behind
the scenes improvements.

    The fake-factory dependency was renamed to faker. If you were
    depending on it through hypothesis[django] or hypothesis[fake-factory]
    without pinning it yourself then it would have failed to install
    properly. This release changes it so that hypothesis[fakefactory]
    (which can now also be installed as hypothesis[faker]) will
    install the renamed faker package instead.

    This release also removed the dependency of hypothesis[django]
    on hypothesis[fakefactory] - it was only being used for emails.
    These now use a custom strategy that isnât from fakefactory.

    As a result you should also see performance improvements of
    tests which generated User objects or other things with email
    fields, as well as better shrinking of email addresses.

    The distribution of code using nested calls to one_of or the
    | operator for combining strategies has been improved, as
    branches are now flattened to give a more uniform distribution.
    Examples using composite or flatmap should now shrink better.

    In particular this will affect things which work by first
    generating a length and then generating that many items, which
    have historically not shrunk very well.

Log message:
Updated py-hypothesis to 3.6.0.

3.6.0 - 2016-10-31

This release reverts Hypothesis to its old pretty printing of lambda
functions based on attempting to extract the source code rather
than decompile the bytecode. This is unfortunately slightly inferior
in some cases and may result in you occasionally seeing things like
lambda x: <unknown> in statistics reports and strategy reprs.

This removes the dependencies on uncompyle6, xdis and spark-parser.

The reason for this is that the new functionality was based on
uncompyle6, which turns out to introduce a hidden GPLed dependency
- it in turn depended on xdis, and although the library was licensed
under the MIT license, it contained some GPL licensed source code
and thus should have been released under the GPL.

My interpretation is that Hypothesis itself was never in violation
of the GPL (because the license it is under, the Mozilla Public
License v2, is fully compatible with being included in a GPL licensed
work), but I have not consulted a lawyer on the subject. Regardless
of the answer to this question, adding a GPLed dependency will
likely cause a lot of users of Hypothesis to inadvertently be in
violation of the GPL.

As a result, if you are running Hypothesis 3.5.x you really should
upgrade to this release immediately.