---
- branch: MAIN
  date: Mon Mar  5 13:52:38 UTC 2018
  files:
  - new: '1.49'
    old: '1.48'
    path: pkgsrc/devel/py-hypothesis/Makefile
    pathrev: pkgsrc/devel/py-hypothesis/Makefile@1.49
    type: modified
  - new: '1.46'
    old: '1.45'
    path: pkgsrc/devel/py-hypothesis/distinfo
    pathrev: pkgsrc/devel/py-hypothesis/distinfo@1.46
    type: modified
  id: 20180305T135238Z.a307fa201c475ce0288099c1eb0bb6d2c87f649c
  log: |
    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.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/py-hypothesis'
  unixtime: '1520257958'
  user: adam