Next | Query returned 36 messages, browsing 1 to 10 | Previous

History of commit frequency

CVS Commit History:


   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.
   2017-09-13 08:26:55 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: update to 3.26.0

3.26.0:
Hypothesis now emits deprecation warnings if you are using the legacy SQLite \ 
example database format, or the tool for merging them. These were already \ 
documented as deprecated, so this doesn't change their deprecation status, only \ 
that we warn about it.
   2017-09-08 13:03:28 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
3.24.1:
This release improves the reduction of examples involving floating point numbers \ 
to produce more human readable examples.
It also has some general purpose changes to the way the minimizer works \ 
internally, which may see some improvement in quality and slow down of test case \ 
reduction in cases that have nothing to do with floating point numbers.

3.24.0:
Hypothesis now emits deprecation warnings if you use example() inside a test \ 
function or strategy definition (this was never intended to be supported, but is \ 
sufficiently widespread that it warrants a deprecation path).
   2017-09-04 19:28:45 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
3.23.2:
This is a small refactoring release that removes a now-unused parameter to an \ 
internal API. It shouldn’t have any user visible effect.

3.23.1:
Hypothesis no longer propagates the dynamic scope of settings into strategy \ 
definitions.

This release is a small change to something that was never part of the public \ 
API and you will almost certainly not notice any effect unless you’re doing \ 
something surprising, but for example the following code will now give a \ 
different answer in some circumstances:

import hypothesis.strategies as st
from hypothesis import settings

CURRENT_SETTINGS = st.builds(lambda: settings.default)
(We don’t actually encourage you writing code like this)

Previously this would have generated the settings that were in effect at the \ 
point of definition of CURRENT_SETTINGS. Now it will generate the settings that \ 
are used for the current test.

It is very unlikely to be significant enough to be visible, but you may also \ 
notice a small performance improvement.
   2017-08-27 14:16:07 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
3.22.0:
This release provides what should be a substantial performance improvement to \ 
numpy arrays generated using provided numpy support, and adds a new fill_value \ 
argument to arrays() to control this behaviour.
   2017-08-19 14:16:20 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
3.18.5:
This is a bugfix release for ~hypothesis.strategies.integers. Previously the \ 
strategy would hit an internal assertion if passed non-integer bounds for \ 
min_value and max_value that had no integers between them. The strategy now \ 
raises InvalidArgument instead.
   2017-08-13 11:46:55 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
3.17.0:
This release documents the previously undocumented phases feature”, making \ 
it part of the official public API. It also updates how the example database is \ 
used. Principally:
* A Phases.reuse argument will now correctly control whether examples from the \ 
database are run (it previously did exactly the wrong thing and controlled \ 
whether examples would be saved).
* Hypothesis will no longer try to rerun all previously failing examples. \ 
Instead it will replay the smallest previously failing example and a selection \ 
of other examples that are likely to trigger any other bugs that will found. \ 
This prevents a previous failure from dominating your tests unnecessarily.
* As a result of the previous change, Hypothesis will be slower about clearing \ 
out old examples from the database that are no longer failing (because it can \ 
only clear out ones that it actually runs).
   2017-08-07 20:00:41 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
3.16.1:
This release makes an implementation change to how Hypothesis handles certain \ 
internal constructs.

The main effect you should see is improvement to the behaviour and performance \ 
of collection types, especially ones with a min_size parameter. Many cases that \ 
would previously fail due to being unable to generate enough valid examples will \ 
now succeed, and other cases should run slightly faster.

3.16.0:
This release introduces a deprecation of the timeout feature. This results in \ 
the following changes:

Creating a settings object with an explicit timeout will emit a deprecation warning.
If your test stops because it hits the timeout (and has not found a bug) then it \ 
will emit a deprecation warning.
There is a new value unlimited which you can import from hypothesis. \ 
settings(timeout=unlimited) will not cause a deprecation warning.
There is a new health check, hung_test, which will trigger after a test has been \ 
running for five minutes if it is not suppressed.

Next | Query returned 36 messages, browsing 1 to 10 | Previous