Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update hypothesis to 3.30.4 #30

Merged
merged 1 commit into from
Sep 27, 2017

Conversation

pyup-bot
Copy link
Contributor

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

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

Changelog

3.30.4


This release makes several changes:

  1. It significantly improves Hypothesis's ability to use coverage information
    to find interesting examples.
  2. It reduces the default max_examples setting from 200 to 100. This takes
    advantage of the improved algorithm meaning fewer examples are typically
    needed to get the same testing and is sufficiently better at covering
    interesting behaviour, and offsets some of the performance problems of
    running under coverage.
  3. Hypothesis will always try to start its testing with an example that is near
    minimized.

The new algorithm for 1 also makes some changes to Hypothesis's low level data
generation which apply even with coverage turned off. They generally reduce the
total amount of data generated, which should improve test performance somewhat.
Between this and 3 you should see a noticeable reduction in test runtime (how
much so depends on your tests and how much example size affects their
performance. On our benchmarks, where data generation dominates, we saw up to
a factor of two performance improvement, but it's unlikely to be that large.


3.30.3


This release fixes some formatting and small typos/grammar issues in the
documentation, specifically the page docs/details.rst, and some inline
docs linked from there.


3.30.2


This release changes Hypothesis's caching approach for functions in
hypothesis.strategies. Previously it would have cached extremely
aggressively and cache entries would never be evicted. Now it adopts a
least-frequently used, least recently used key invalidation policy, and is
somewhat more conservative about which strategies it caches.

This should cause some workloads (anything that creates strategies based on
dynamic values, e.g. using flatmap or composite) to see a significantly lower
memory usage.


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

Happy merging! 🤖

@coveralls
Copy link

coveralls commented Sep 27, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 0b54354 on pyup-update-hypothesis-3.30.1-to-3.30.4 into 5c3ffca on master.

Repository owner deleted a comment from coveralls Sep 27, 2017
Repository owner deleted a comment from coveralls Sep 27, 2017
@jason-neal jason-neal merged commit 4e445f2 into master Sep 27, 2017
@jason-neal jason-neal deleted the pyup-update-hypothesis-3.30.1-to-3.30.4 branch September 29, 2017 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants