Hello community,

here is the log from the commit of package python-hypothesis for 
openSUSE:Factory checked in at 2018-06-05 12:49:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-hypothesis (Old)
 and      /work/SRC/openSUSE:Factory/.python-hypothesis.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-hypothesis"

Tue Jun  5 12:49:00 2018 rev:19 rq:613244 version:3.57.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-hypothesis/python-hypothesis.changes      
2018-03-09 10:34:28.804856815 +0100
+++ /work/SRC/openSUSE:Factory/.python-hypothesis.new/python-hypothesis.changes 
2018-06-05 12:49:01.994162470 +0200
@@ -1,0 +2,266 @@
+Thu May 31 02:56:55 UTC 2018 - [email protected]
+
+- Update to 3.57.0
+  * Using an unordered collection with the 
:func:`~hypothesis.strategies.permutations`
+    strategy has been deprecated because the order in which e.g. a set shrinks 
is
+    arbitrary. This may cause different results between runs.
+- Update to 3.56.10 - 2018-05-16
+  * This release makes :obj:`~hypothesis.settings.define_setting`
+    aprivate method, which has the effect of hiding it from the
+    documentation.
+- Update to 3.56.9
+  * This is another release with no functionality changes as part of changes to
+    Hypothesis's new release tagging scheme.
+- Update to 3.56.8
+  * This is a release with no functionality changes that moves Hypothesis over 
to
+    anew release tagging scheme.
+- Update to 3.56.7
+  * This release provides a performance improvement for most tests, but in
+    particular users of ``sampled_from`` who don't have numpy installed should 
see
+    asignificant performance improvement.
+- Update to 3.56.6
+  * This patch contains further internal work to support Mypy.
+    There are no user-visible changes... yet.
+- Update to 3.56.5
+  * This patch contains some internal refactoring to run :pypi:`mypy` in CI.
+    There are no user-visible changes.
+- Update to 3.56.4
+  * This release involves some very minor internal clean up and should have no
+    user visible effect at all.
+- Update to 3.56.3
+  * This release fixes a problem introduced in :ref:`3.56.0 <v3.56.0>` where
+    setting the hypothesis home directory (through currently undocumented
+    means) would no longer result in the default database location living
+    in the new home directory.
+- Update to 3.56.2
+  * This release fixes a problem introduced in :ref:`3.56.0 <v3.56.0>` where
+    setting :obj:`~hypothesis.settings.max_examples` to ``1`` would result in 
tests
+    failing with ``Unsatisfiable``. This problem could also occur in other 
harder
+    to trigger circumstances (e.g. by setting it to a low value, having a hard 
to
+    satisfy assumption, and disabling health checks).
+- Update to 3.56.1
+  * This release fixes a problem that was introduced in :ref:`3.56.0 
<v3.56.0>`:
+    Use of the :envvar:`HYPOTHESIS_VERBOSITY_LEVEL` environment variable was, 
rather
+    than deprecated, actually broken due to being read before various setup
+    the deprecation path needed was done. It now works correctly (and emits a
+    deprecation warning).
+- Update to 3.56.0
+  * This release deprecates several redundant or internally oriented
+    :class:`~hypothesis.settings`, working towards an orthogonal set of
+    configuration options that are widely useful *without* requiring any
+    knowledge of our internals (:issue:`535`).
+    + Deprecated settings that no longer have any effect are no longer
+      shown in the ``__repr__`` unless set to a non-default value.
+    + :obj:`~hypothesis.settings.perform_health_check` is deprecated, as it
+      duplicates :obj:`~hypothesis.settings.suppress_health_check`.
+    + :obj:`~hypothesis.settings.max_iterations` is deprecated and disabled,
+      because we can usually get better behaviour from an internal heuristic
+      than a user-controlled setting.
+    + :obj:`~hypothesis.settings.min_satisfying_examples` is deprecated and
+      disabled, due to overlap with the
+      :obj:`~hypothesis.settings.HealthCheck.filter_too_much` healthcheck
+      and poor interaction with :obj:`~hypothesis.settings.max_examples`.
+    + :envvar:`HYPOTHESIS_VERBOSITY_LEVEL` is now deprecated.  Set
+      :obj:`~hypothesis.settings.verbosity` through the profile system instead.
+    + Examples tried by :func:`~hypothesis.find` are now reported at ``debug``
+      verbosity level (as well as ``verbose`` level).
+- Update to 3.55.6
+  * This release fixes a somewhat obscure condition (:issue:`1230`) under 
which you
+    could occasionally see a failing test trigger an assertion error inside
+    Hypothesis instead of failing normally.
+- Update to 3.55.5
+  * This patch fixes one possible cause of :issue:`966`.  When running
+    Python 2 with hash randomisation, passing a :obj:`python:bytes` object
+    to :func:`python:random.seed` would use ``version=1``, which broke
+    :obj:`~hypothesis.settings.derandomize` (because the seed depended on
+    arandomised hash).  If :obj:`~hypothesis.settings.derandomize` is
+    *still* nondeterministic for you, please open an issue.
+- Update to 3.55.4
+  * This patch makes a variety of minor improvements to the documentation,
+    and improves a few validation messages for invalid inputs.
+- Update to 3.55.3
+  * This release updates the URL metadata associated with the PyPI package 
(again).
+    It has no other user visible effects.
+- Update to 3.55.2
+  * This release updates the URL metadata associated with the PyPI package.
+    It has no other user visible effects.
+- Update to 3.55.1
+  * This patch relaxes constraints on the expected values returned
+    by the standard library function :func:`hypot` and the internal
+    helper function :func:`~hypotheses.internal.cathetus`, this to
+    fix near-exact test-failures on some 32-bit systems.
+- Update to 3.55.0
+  * This release includes several improvements to the handling of the
+    :obj:`~hypothesis.settings.database` setting.
+    + The :obj:`~hypothesis.settings.database_file` setting was a historical
+      artefact, and you should just use :obj:`~hypothesis.settings.database`
+      directly.
+    + The :envvar:`HYPOTHESIS_DATABASE_FILE` environment variable is
+      deprecated, in favor of :meth:`~hypothesis.settings.load_profile` and
+      the :obj:`~hypothesis.settings.database` setting.
+    + If you have not configured the example database at all and the default
+      location is not usable (due to e.g. permissions issues), Hypothesis
+      will fall back to an in-memory database.  This is not persisted between
+      sessions, but means that the defaults work on read-only filesystems.
+- Update to 3.54.0
+  * This release improves the :func:`~hypotheses.strategies.complex_numbers`
+    strategy, which now supports ``min_magnitude`` and ``max_magnitude``
+    arguments, along with ``allow_nan`` and ``allow_infinity`` like for
+    :func:`~hypotheses.strategies.floats`.
+    Thanks to J.J. Green for this feature.
+- Update to 3.53.0
+  * This release removes support for Django 1.8, which reached end of life on
+    2018-04-01.  You can see Django's release and support schedule
+    `on the Django Project website 
<https://www.djangoproject.com/download/#supported-versions>`_.
+- Update to 3.52.3
+  * This patch fixes the :obj:`~hypothesis.settings.min_satisfying_examples` 
settings
+    documentation, by explaining that example shrinking is tracked at the level
+    of the underlying bytestream rather than the output value.
+  * The output from :func:`~hypothesis.find` in verbose mode has also been
+    adjusted - see :ref:`the example session <verbose-output>` - to avoid
+    duplicating lines when the example repr is constant, even if the underlying
+    representation has been shrunken.
+- Update to 3.52.2
+  * This release improves the output of failures with
+    :ref:`rule based stateful testing <rulebasedstateful>` in two ways:
+     The output from it is now usually valid Python code.
+     When the same value has two different names because it belongs to two 
different
+     bundles, it will now display with the name associated with the correct 
bundle
+     for a rule argument where it is used.
+- Update to 3.52.1
+  * This release improves the behaviour of  :doc:`stateful testing <stateful>`
+    in two ways:
+    Previously some runs would run no steps (:issue:`376`). This should no 
longer
+    happen.
+    RuleBasedStateMachine tests which used bundles extensively would often 
shrink
+    terribly. This should now be significantly improved, though there is likely
+    a lot more room for improvement.
+  * This release also involves a low level change to how ranges of integers are
+    handles which may result in other improvements to shrink quality in some 
cases.
+- Update to 3.52.0
+  * This release deprecates use of :func:`@settings(...) <hypothesis.settings>`
+    as a decorator, on functions or methods that are not also decorated with
+    :func:`@given <hypothesis.given>`.  You can still apply these decorators
+    in any order, though you should only do so once each.
+  * Applying :func:`@given <hypothesis.given>` twice was already deprecated, 
and
+    applying :func:`@settings(...) <hypothesis.settings>` twice is deprecated 
in
+    this release and will become an error in a future version. Neither could 
ever
+    be used twice to good effect.
+  * Using :func:`@settings(...) <hypothesis.settings>` as the sole decorator on
+    atest is completely pointless, so this common usage error will become an
+    error in a future version of Hypothesis.
+- Update to 3.51.0
+  * This release deprecates the ``average_size`` argument to
+    :func:`~hypothesis.strategies.lists` and other collection strategies.
+    You should simply delete it wherever it was used in your tests, as it
+    no longer has any effect.
+    In early versions of Hypothesis, the ``average_size`` argument was treated
+    as a hint about the distribution of examples from a strategy.  Subsequent
+    improvements to the conceptual model and the engine for generating and
+    shrinking examples mean it is more effective to simply describe what
+    constitutes a valid example, and let our internals handle the distribution.
+- Update to 3.50.3
+  * This patch contains some internal refactoring so that we can run
+    with warnings as errors in CI.
+- Update to 3.50.2
+  * This has no user-visible changes except one slight formatting change to 
one docstring, to avoid a deprecation warning.
+- Update to 3.50.1
+  * This patch fixes an internal error introduced in :ref:`3.48.0 <v3.48.0>`, 
where a check
+    for the Django test runner would expose import-time errors in Django
+    configuration (:issue:`1167`).
+- Update to 3.50.0
+  * This release improves validation of numeric bounds for some strategies.
+    + :func:`~hypothesis.strategies.integers` and 
:func:`~hypothesis.strategies.floats`
+      now raise ``InvalidArgument`` if passed a ``min_value`` or ``max_value``
+      which is not an instance of :class:`~python:numbers.Real`, instead of
+      various internal errors.
+    + :func:`~hypothesis.strategies.floats` now converts its bounding values to
+      the nearest float above or below the min or max bound respectively, 
instead
+      of just casting to float.  The old behaviour was incorrect in that you 
could
+      generate ``float(min_value)``, even when this was less than ``min_value``
+      itself (possible with eg. fractions).
+    + When both bounds are provided to :func:`~hypothesis.strategies.floats` 
but
+      there are no floats in the interval, such as ``[(2**54)+1 .. 
(2**55)-1]``,
+      InvalidArgument is raised.
+    + :func:`~hypothesis.strategies.decimals` gives a more useful error message
+      if passed a string that cannot be converted to 
:class:`~python:decimal.Decimal`
+      in a context where this error is not trapped.
+     Code that previously **seemed** to work may be explicitly broken if there
+     were no floats between ``min_value`` and ``max_value`` (only possible with
+     non-float bounds), or if a bound was not a :class:`~python:numbers.Real`
+     number but still allowed in :obj:`python:math.isnan` (some custom classes
+     with a ``__float__`` method).
+- Update to 3.49.1
+  * This patch fixes our tests for Numpy dtype strategies on big-endian 
platforms,
+    where the strategy behaved correctly but the test assumed that the native 
byte
+    order was little-endian.
+    There is no user impact unless you are running our test suite on big-endian
++++ 69 more lines (skipped)
++++ between 
/work/SRC/openSUSE:Factory/python-hypothesis/python-hypothesis.changes
++++ and 
/work/SRC/openSUSE:Factory/.python-hypothesis.new/python-hypothesis.changes

Old:
----
  hypothesis-3.45.3.tar.gz

New:
----
  LICENSE.txt
  hypothesis-3.57.0.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-hypothesis.spec ++++++
--- /var/tmp/diff_new_pack.zxYeS6/_old  2018-06-05 12:49:02.474144882 +0200
+++ /var/tmp/diff_new_pack.zxYeS6/_new  2018-06-05 12:49:02.474144882 +0200
@@ -24,24 +24,15 @@
 %endif
 %bcond_without python2
 Name:           python-hypothesis
-Version:        3.45.3
+Version:        3.57.0
 Release:        0
 Summary:        A library for property based testing
 License:        MPL-2.0
 Group:          Development/Languages/Python
 Url:            https://github.com/HypothesisWorks/hypothesis-python
 Source:         
https://files.pythonhosted.org/packages/source/h/hypothesis/hypothesis-%{version}.tar.gz
+Source10:       
https://raw.githubusercontent.com/HypothesisWorks/hypothesis/hypothesis-python-%{version}/LICENSE.txt
 Patch0:         %{name}-build.patch
-#BuildRequires:  %{python_module Django >= 1.8}
-#BuildRequires:  %{python_module Faker >= 0.7.0}
-#BuildRequires:  %{python_module attrs}
-#BuildRequires:  %{python_module coverage}
-#BuildRequires:  %{python_module flaky}
-#BuildRequires:  %{python_module mock}
-#BuildRequires:  %{python_module numpy >= 1.9.0}
-#BuildRequires:  %{python_module pandas}
-#BuildRequires:  %{python_module pytest >= 2.8.0}
-#BuildRequires:  %{python_module pytz}
 BuildRequires:  %{python_module setuptools >= 36}
 BuildRequires:  fdupes
 BuildRequires:  python-rpm-macros
@@ -81,6 +72,7 @@
 # remove py2/3 and django tests as they fail
 rm -rf tests/py3 tests/py2 tests/django
 %patch0 -p1
+cp %{SOURCE10} .
 
 %build
 %python_build
@@ -89,12 +81,9 @@
 %python_install
 %python_expand %fdupes -s %{buildroot}%{$python_sitelib}
 
-# Flaky a lot in OBS unable to reliably test
-#%%check
-#%%python_exec setup.py test
-
 %files %{python_files}
 %doc README.rst
+%license LICENSE.txt
 %{python_sitelib}/*
 
 %changelog

++++++ LICENSE.txt ++++++
Copyright (c) 2013, David R. MacIver

All code in this repository except where explicitly noted otherwise is released
under the Mozilla Public License v 2.0. You can obtain a copy at 
http://mozilla.org/MPL/2.0/.

Some code in this repository comes from other projects. Where applicable, the
original copyright and license are noted and any modifications made are released
dual licensed with the original license.
++++++ hypothesis-3.45.3.tar.gz -> hypothesis-3.57.0.tar.gz ++++++
++++ 6308 lines of diff (skipped)


Reply via email to