./devel/py-hypothesis, Python library for property based testing

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 3.42.2, Package name: py27-hypothesis-3.42.2, Maintainer: pkgsrc-users

Hypothesis is a library for testing your Python code against a much
larger range of examples than you would ever want to write by hand.
It's based on the Haskell library, Quickcheck, and is designed to
integrate seamlessly into your existing Python unit testing work
flow.

Hypothesis is both extremely practical and also advances the state
of the art of unit testing by some way. It's easy to use, stable,
and extremely powerful. If you're not using Hypothesis to test your
project then you're missing out.


Required to run:
[devel/py-setuptools] [databases/py-sqlite3] [devel/py-coverage] [lang/python27] [devel/py-enum34] [devel/py-attrs]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 3fc623247fa461f7b33c9deacbbcec619753ea12
RMD160: 728c9fd5c730a0d85792d1ca60e455991a6b001a
Filesize: 129.649 KB

Version history: (Expand)


CVS history: (Expand)


   2017-12-13 09:17:10 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 3.42.2

3.42.2:
This patch fixes :issue:1017, where instances of a list or tuple subtype used as \ 
an argument to a strategy would be coerced to tuple.

3.42.1:
This release has some internal cleanup, which makes reading the code more \ 
pleasant and may shrink large examples slightly faster.

3.42.0:
This release deprecates :ref:faker-extra, which was designed as a transition \ 
strategy but does not support example shrinking or coverage-guided discovery.
   2017-11-16 08:59:55 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 3.37.0

3.37.0:
This is a deprecation release for some health check related features.

The following are now deprecated:

* Passing exception_in_generation to suppress_health_check. This no longer does \ 
anything even when passed - All errors that occur during data generation will \ 
now be immediately reraised rather than going through the health check \ 
mechanism.

* Passing random_module to suppress_health_check. This hasn’t done anything \ 
for a long time, but was never explicitly deprecated. Hypothesis always seeds \ 
the random module when running @given tests, so this is no longer an error and \ 
suppressing it doesn’t do anything.

* Passing non-HealthCheck values in suppress_health_check. This was previously \ 
allowed but never did anything useful.

In addition, passing a non-iterable value as suppress_health_check will now \ 
raise an error immediately (it would never have worked correctly, but it would \ 
previously have failed later). Some validation error messages have also been \ 
updated.
   2017-11-09 08:41:44 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 3.36.0

3.36.0:
This release adds a setting to the public API, and does some internal cleanup:
The :attr:`~hypothesis.settings.derandomize` setting is now documented
Removed - and disallowed - all 'bare excepts' in Hypothesis
Documented the :attr:`~hypothesis.settings.strict` setting as deprecated, and \ 
updated the build so our docs always match deprecations in the code.
   2017-11-06 11:39:08 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-hypothesis: updated to 3.34.1

3.34.1:

This patch updates the documentation to suggest :func:`builds(callable) \ 
<hypothesis.strategies.builds>` instead of :func:`just(callable()) \ 
<hypothesis.strategies.just>`.

3.34.0:

Hypothesis now emits deprecation warnings if you apply :func:`@given \ 
<hypothesis.given>` more than once to a target.

Applying :func:`@given <hypothesis.given>` repeatedly wraps the target \ 
multiple times. Each wrapper will search the space of of possible parameters \ 
separately. This is equivalent but will be much more inefficient than doing it \ 
with a single call to :func:`@given <hypothesis.given>`.

For example, instead of @given(booleans()) @given(integers()), you could write \ 
@given(booleans(), integers())
   2017-11-02 08:16:35 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-hypothesis: updated to 3.33.1

3.33.1:

This is a bugfix release:
* :func:`~hypothesis.strategies.builds` would try to infer a strategy for \ 
required positional arguments of the target from type hints, even if they had \ 
been given to :func:`~hypothesis.strategies.builds` as positional arguments \ 
(:issue:`946`). Now it only infers missing required arguments.
* An internal introspection function wrongly reported self as a required \ 
argument for bound methods, which might also have affected \ 
:func:`~hypothesis.strategies.builds`. Now it knows better.
   2017-10-16 20:35:19 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: update to 3.33.0

3.33.0:
This release supports strategy inference for more field types in Django models() \ 
- you can now omit an argument for Date, Time, Duration, Slug, IP Address, and \ 
UUID fields.

Strategy generation for fields with grouped choices now selects choices from \ 
each group, instead of selecting from the group names.
   2017-10-05 08:48:38 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-hypothesis: update to 3.31.2:

This release fixes some formatting and small typos/grammar issues in the \ 
documentation, specifically the page docs/settings.rst, and the inline docs for \ 
the various settings.
   2017-09-30 15:12:04 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: update to 3.31.1

3.31.1:

This release improves the handling of deadlines so that they act better with the \ 
shrinking process. This fixes :issue:`892`.

This involves two changes:

1. The deadline is raised during the initial generation and shrinking, and then \ 
lowered to the set value for final replay. This restricts our attention to \ 
examples which exceed the deadline by a more significant margin, which increases \ 
their reliability.

2. When despite the above a test still becomes flaky because it is significantly \ 
faster on rerun than it was on its first run, the error message is now more \ 
explicit about the nature of this problem, and includes both the initial test \ 
run time and the new test run time.

In addition, this release also clarifies the documentation of the deadline \ 
setting slightly to be more explicit about where it applies.