kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/py-hypothesis/PLIST

312 lines
15 KiB
Text
Raw Normal View History

py-hypothesis: updated to 6.29.3 6.29.3 This patch fixes a bug in mutually_broadcastable_shapes(), which restricted the patterns of singleton dimensions that could be generated for dimensions that extended beyond base_shape. 6.29.2 This patch clarifies our pretty-printing of DataFrames. 6.29.1 This patch documents timezones() Windows-only requirement for the tzdata package, and ensures that pip install hypothesis[zoneinfo] will install the latest version. 6.29.0 This release teaches builds() to use deferred() when resolving unrecognised type hints, so that you can conveniently register strategies for recursive types with constraints on some arguments: class RecursiveClass: def __init__(self, value: int, next_node: typing.Optional["SomeClass"]): assert value > 0 self.value = value self.next_node = next_node st.register_type_strategy( RecursiveClass, st.builds(RecursiveClass, value=st.integers(min_value=1)) ) 6.28.1 This release fixes some internal calculations related to collection sizes. 6.28.0 This release modifies our pytest plugin, to avoid importing Hypothesis and therefore triggering Hypothesis’ entry points for test suites where Hypothesis is installed but not actually used. 6.27.3 This release fixes issue 3080, where from_type() failed on unions containing PEP 585 builtin generic types (like list[int]) in Python 3.9 and later. 6.27.2 This patch makes the hypothesis codemod command somewhat faster.
2021-12-02 12:15:26 +01:00
@comment $NetBSD: PLIST,v 1.36 2021/12/02 11:15:26 adam Exp $
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
bin/hypothesis
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/${EGG_INFODIR}/PKG-INFO
${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt
${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt
${PYSITELIB}/${EGG_INFODIR}/entry_points.txt
${PYSITELIB}/${EGG_INFODIR}/not-zip-safe
${PYSITELIB}/${EGG_INFODIR}/requires.txt
${PYSITELIB}/${EGG_INFODIR}/top_level.txt
py-hypothesis: updated to 6.29.3 6.29.3 This patch fixes a bug in mutually_broadcastable_shapes(), which restricted the patterns of singleton dimensions that could be generated for dimensions that extended beyond base_shape. 6.29.2 This patch clarifies our pretty-printing of DataFrames. 6.29.1 This patch documents timezones() Windows-only requirement for the tzdata package, and ensures that pip install hypothesis[zoneinfo] will install the latest version. 6.29.0 This release teaches builds() to use deferred() when resolving unrecognised type hints, so that you can conveniently register strategies for recursive types with constraints on some arguments: class RecursiveClass: def __init__(self, value: int, next_node: typing.Optional["SomeClass"]): assert value > 0 self.value = value self.next_node = next_node st.register_type_strategy( RecursiveClass, st.builds(RecursiveClass, value=st.integers(min_value=1)) ) 6.28.1 This release fixes some internal calculations related to collection sizes. 6.28.0 This release modifies our pytest plugin, to avoid importing Hypothesis and therefore triggering Hypothesis’ entry points for test suites where Hypothesis is installed but not actually used. 6.27.3 This release fixes issue 3080, where from_type() failed on unions containing PEP 585 builtin generic types (like list[int]) in Python 3.9 and later. 6.27.2 This patch makes the hypothesis codemod command somewhat faster.
2021-12-02 12:15:26 +01:00
${PYSITELIB}/_hypothesis_pytestplugin.py
${PYSITELIB}/_hypothesis_pytestplugin.pyc
${PYSITELIB}/_hypothesis_pytestplugin.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/__init__.py
${PYSITELIB}/hypothesis/__init__.pyc
${PYSITELIB}/hypothesis/__init__.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/_error_if_old.py
${PYSITELIB}/hypothesis/_error_if_old.pyc
${PYSITELIB}/hypothesis/_error_if_old.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/_settings.py
${PYSITELIB}/hypothesis/_settings.pyc
${PYSITELIB}/hypothesis/_settings.pyo
${PYSITELIB}/hypothesis/configuration.py
${PYSITELIB}/hypothesis/configuration.pyc
${PYSITELIB}/hypothesis/configuration.pyo
${PYSITELIB}/hypothesis/control.py
${PYSITELIB}/hypothesis/control.pyc
${PYSITELIB}/hypothesis/control.pyo
${PYSITELIB}/hypothesis/core.py
${PYSITELIB}/hypothesis/core.pyc
${PYSITELIB}/hypothesis/core.pyo
${PYSITELIB}/hypothesis/database.py
${PYSITELIB}/hypothesis/database.pyc
${PYSITELIB}/hypothesis/database.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/entry_points.py
${PYSITELIB}/hypothesis/entry_points.pyc
${PYSITELIB}/hypothesis/entry_points.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/errors.py
${PYSITELIB}/hypothesis/errors.pyc
${PYSITELIB}/hypothesis/errors.pyo
${PYSITELIB}/hypothesis/executors.py
${PYSITELIB}/hypothesis/executors.pyc
${PYSITELIB}/hypothesis/executors.pyo
${PYSITELIB}/hypothesis/extra/__init__.py
${PYSITELIB}/hypothesis/extra/__init__.pyc
${PYSITELIB}/hypothesis/extra/__init__.pyo
py-hypothesis: updated to 6.21.0 6.21.0 - 2021-09-11 This release introduces strategies for array/tensor libraries adopting the Array API standard. They are available in the hypothesis.extra.array_api extra, and work much like the existing strategies for NumPy. 6.20.1 - 2021-09-10 This patch fixes issue 961, where calling given() inline on a bound method would fail to handle the self argument correctly. 6.20.0 - 2021-09-09 This release allows slices() to generate step=None, and fixes an off-by-one error where the start index could be equal to size. This works fine for all Python sequences and Numpy arrays, but is undefined behaviour in the Array API standard. 6.19.0 - 2021-09-08 This release makes stateful testing more likely to tell you if you do something unexpected and unsupported: The return_value health check now applies to rule() and initialize() rules, if they don’t have target bundles, as well as invariant(). Using a consumes() bundle as a target is deprecated, and will be an error in a future version. If existing code triggers these new checks, check for related bugs and misunderstandings - these patterns never had any effect. 6.18.0 - 2021-09-06 This release teaches from_type() a neat trick: when resolving an typing.Annotated type, if one of the annotations is a strategy object we use that as the inferred strategy. For example: PositiveInt = Annotated[int, st.integers(min_value=1)] If there are multiple strategies, we use the last outer-most annotation. See issue 2978 and pull request 3082 for discussion. Requires Python 3.9 or later for get_type_hints(..., include_extras=False). 6.17.4 - 2021-08-31 This patch makes unique arrays() much more efficient, especially when there are only a few valid elements - such as for eight-bit integers. 6.17.3 - 2021-08-30 This patch fixes the repr of array_shapes(). 6.17.2 - 2021-08-30 This patch wraps some internal helper code in our proxies decorator to prevent mutations of method docstrings carrying over to other instances of the respective methods. 6.17.1 - 2021-08-29 This patch moves some internal helper code in preparation for issue 3065. There is no user-visible change, unless you depended on undocumented internals. 6.17.0 - 2021-08-27 This release adds type annotations to the stateful testing API. Thanks to Ruben Opdebeeck for this contribution! 6.16.0 - 2021-08-27 This release adds the DrawFn type as a reusable type hint for the draw argument of @composite functions. Thanks to Ruben Opdebeeck for this contribution! 6.15.0 - 2021-08-22 This release emits a more useful error message when @given() is applied to a coroutine function, i.e. one defined using async def. This was previously only handled by the generic return_value health check, which doesn’t direct you to use either a custom executor or a library such as pytest-trio or pytest-asyncio to handle it for you. 6.14.9 - 2021-08-20 This patch fixes a regression in Hypothesis 6.14.8, where from_type() failed to resolve types which inherit from multiple parametrised generic types, affecting the returns package. 6.14.8 - 2021-08-16 This patch ensures that registering a strategy for a subclass of a a parametrised generic type such as class Lines(Sequence[str]): will not “leak” into unrelated strategies such as st.from_type(Sequence[int]). Unfortunately this fix requires PEP 560, meaning Python 3.7 or later. 6.14.7 - 2021-08-14 This patch fixes issue 3050, where attrs classes could cause an internal error in the ghostwriter. 6.14.6 - 2021-08-07 This patch improves the error message for issue 3016, where PEP 585 builtin generics with self-referential forward-reference strings cannot be resolved to a strategy by from_type(). 6.14.5 - 2021-07-27 This patch fixes hypothesis.strategies._internal.types.is_a_new_type. It was failing on Python 3.10.0b4, where NewType is a function. 6.14.4 - 2021-07-26 This patch fixes from_type() and register_type_strategy() for typing.NewType on Python 3.10, which changed the underlying implementation (see bpo-44353 for details). 6.14.3 - 2021-07-18 This patch updates our autoformatting tools, improving our code style without any API changes. 6.14.2 - 2021-07-12 This patch ensures that we shorten tracebacks for tests which fail due to inconsistent data generation between runs (i.e. raise Flaky). 6.14.1 - 2021-07-02 This patch updates some internal type annotations. There is no user-visible change.
2021-09-12 11:53:53 +02:00
${PYSITELIB}/hypothesis/extra/_array_helpers.py
${PYSITELIB}/hypothesis/extra/_array_helpers.pyc
${PYSITELIB}/hypothesis/extra/_array_helpers.pyo
${PYSITELIB}/hypothesis/extra/array_api.py
${PYSITELIB}/hypothesis/extra/array_api.pyc
${PYSITELIB}/hypothesis/extra/array_api.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/extra/cli.py
${PYSITELIB}/hypothesis/extra/cli.pyc
${PYSITELIB}/hypothesis/extra/cli.pyo
py-hypothesis: update to 5.46.0. 5.46.0 - 2021-01-04 This release upgrades from_type(), to infer strategies for type-annotated arguments even if they have defaults when it otherwise falls back to builds() (issue #2708). 5.45.0 - 2021-01-04 This release adds the hypothesis[codemods] extra, which you can use to check for and automatically fix issues such as use of deprecated Hypothesis APIs (issue #2705). 5.44.0 - 2021-01-03 This patch fixes from_type() with the typing_extensions Literal backport on Python 3.6. 5.43.9 - 2021-01-02 This patch fixes issue #2722, where certain orderings of register_type_strategy(), ForwardRef, and from_type() could trigger an internal error. 5.43.8 - 2021-01-02 This patch makes some strategies for collections with a uniqueness constraint much more efficient, including dictionaries(keys=sampled_from(...), values=..) and lists(tuples(sampled_from(...), ...), unique_by=lambda x: x[0]). (related to issue #2036) 5.43.7 - 2021-01-02 This patch extends our faster special case for sampled_from() elements in unique lists() to account for chains of .map(...) and .filter(...) calls (issue #2036). 5.43.6 - 2021-01-02 This patch improves the type annotations on assume() and @reproduce_failure(). 5.43.5 - 2021-01-01 This patch updates our copyright headers to include 2021. Happy new year! 5.43.4 - 2020-12-24 This change fixes a documentation error in the database setting. The previous documentation suggested that callers could specify a database path string, or the special string ":memory:", but this setting has never actually allowed string arguments. Permitted values are None, and instances of ExampleDatabase. 5.43.3 - 2020-12-11 This patch fixes issue #2696, an internal error triggered when the @example decorator was used and the verbosity setting was quiet. 5.43.2 - 2020-12-10 This patch improves the error message from the data_frames() strategy when both the rows and columns arguments are given, but there is a missing entry in rows and the corresponding column has no fill value (issue #2678). 5.43.1 - 2020-12-10 This patch improves the error message if builds() is passed an Enum which cannot be called without arguments, to suggest using sampled_from() (issue #2693). 5.43.0 - 2020-12-09 This release adds new timezones() and timezone_keys() strategies (issue #2630) based on the new zoneinfo module in Python 3.9. pip install hypothesis[zoneinfo] will ensure that you have the appropriate backports installed if you need them.
2021-01-04 12:55:03 +01:00
${PYSITELIB}/hypothesis/extra/codemods.py
${PYSITELIB}/hypothesis/extra/codemods.pyc
${PYSITELIB}/hypothesis/extra/codemods.pyo
py-hypothesis: updated to 3.59.0 3.59.0: This release adds the :func:~hypothesis.strategies.emails strategy, which generates unicode strings representing an email address. 3.58.1: This improves the shrinker. It can now reorder examples: 3 1 2 becomes 1 2 3. 3.58.0: This adds a new extra :py:func:~hypothesis.extra.dateutil.timezones strategy that generates dateutil timezones. Depends on :pypi:python-dateutil.
2018-06-16 14:09:13 +02:00
${PYSITELIB}/hypothesis/extra/dateutil.py
${PYSITELIB}/hypothesis/extra/dateutil.pyc
${PYSITELIB}/hypothesis/extra/dateutil.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/extra/django/__init__.py
${PYSITELIB}/hypothesis/extra/django/__init__.pyc
${PYSITELIB}/hypothesis/extra/django/__init__.pyo
py-hypothesis: updated to 4.4.3 4.4.3: This release fixes an open file leak that used to cause ResourceWarnings. 4.4.2: This release changes Hypothesis's internal approach to caching the results of executing test cases. The result should be that it is now significantly less memory hungry, especially when shrinking large test cases. Some tests may get slower or faster depending on whether the new or old caching strategy was well suited to them, but any change in speed in either direction should be minor. 4.4.1: This patch tightens up some of our internal heuristics to deal with shrinking floating point numbers, which will now run in fewer circumstances. You are fairly unlikely to see much difference from this, but if you do you are likely to see shrinking become slightly faster and/or producing slightly worse results. 4.4.0: This release adds the :func:~hypothesis.extra.django.from_form function, which allows automatic testing against Django forms. (:issue:35) 4.3.0: This release deprecates HealthCheck.hung_test and disables the associated runtime check for tests that ran for more than five minutes. Such a check is redundant now that we enforce the deadline and max_examples setting, which can be adjusted independently. 4.2.0: This release adds a new module, hypothesis.extra.lark, which you can use to generate strings matching a context-free grammar. In this initial version, only :pypi:lark-parser EBNF grammars are supported, by the new :func:hypothesis.extra.lark.from_lark function. 4.1.2: This patch fixes a very rare overflow bug (:issue:1748) which could raise an InvalidArgument error in :func:~hypothesis.strategies.complex_numbers even though the arguments were valid. 4.1.1: This release makes some improvements to internal code organisation and documentation and has no impact on behaviour. 4.1.0: This release adds :func:~hypothesis.register_random, which registers random.Random instances or compatible objects to be seeded and reset by Hypothesis to ensure that test cases are deterministic. We still recommend explicitly passing a random.Random instance from :func:~hypothesis.strategies.randoms if possible, but registering a framework-global state for Hypothesis to manage is better than flaky tests! 4.0.2: This patch fixes :issue:1387, where bounded :func:~hypothesis.strategies.integers with a very large range would almost always generate very large numbers. Now, we usually use the same tuned distribution as unbounded :func:~hypothesis.strategies.integers. 4.0.1: This release randomizes the order in which the shrinker tries some of its initial normalization operations. You are unlikely to see much difference as a result unless your generated examples are very large. In this case you may see some performance improvements in shrinking. 4.0.0: Welcome to the next major version of Hypothesis! There are no new features here, as we release those in minor versions. Instead, 4.0 is a chance for us to remove deprecated features (many already converted into no-ops), and turn a variety of warnings into errors. If you were running on the last version of Hypothesis 3.x without any Hypothesis deprecation warnings (or using private APIs), this will be a very boring upgrade. In fact, nothing will change for you at all. Per :ref:our deprecation policy <deprecation-policy>, warnings added in the last six months (after 2018-07-05) have not been converted to errors. Removals hypothesis.extra.datetime has been removed, replaced by the core date and time strategies. hypothesis.extra.fakefactory has been removed, replaced by general expansion of Hypothesis' strategies and the third-party ecosystem. The SQLite example database backend has been removed. Settings The :obj:~hypothesis.settings.deadline is now enforced by default, rather than just emitting a warning when the default (200 milliseconds per test case) deadline is exceeded. The database_file setting has been removed; use :obj:~hypothesis.settings.database. The perform_health_check setting has been removed; use :obj:~hypothesis.settings.suppress_health_check. The max_shrinks setting has been removed; use :obj:~hypothesis.settings.phases to disable shrinking. The min_satisfying_examples, max_iterations, strict, timeout, and use_coverage settings have been removed without user-configurable replacements. Strategies The elements argument is now required for collection strategies. The average_size argument was a no-op and has been removed. Date and time strategies now only accept min_value and max_value for bounds. :func:~hypothesis.strategies.builds now requires that the thing to build is passed as the first positional argument. Alphabet validation for :func:~hypothesis.strategies.text raises errors, not warnings, as does category validation for :func:~hypothesis.strategies.characters. The choices() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data with :func:~hypothesis.strategies.sampled_from, so choice(elements) becomes data.draw(sampled_from(elements)). The streaming() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data and replace iterating over the stream with data.draw() calls. :func:~hypothesis.strategies.sampled_from and :func:~hypothesis.strategies.permutations raise errors instead of warnings if passed a collection that is not a sequence. Miscellaneous Applying :func:@given <hypothesis.given> to a test function multiple times was really inefficient, and now it's also an error. Using the .example() method of a strategy (intended for interactive exploration) within another strategy or a test function always weakened data generation and broke shrinking, and now it's an error too. The HYPOTHESIS_DATABASE_FILE environment variable is no longer supported, as the database_file setting has been removed. The HYPOTHESIS_VERBOSITY_LEVEL environment variable is no longer supported. You can use the --hypothesis-verbosity pytest argument instead, or write your own setup code using the settings profile system to replace it. Using :func:@seed <hypothesis.seed> or :obj:derandomize=True <hypothesis.settings.derandomize> now forces :obj:database=None <hypothesis.settings.database> to ensure results are in fact reproducible. If :obj:~hypothesis.settings.database is not None, doing so also emits a HypothesisWarning. Unused exception types have been removed from hypothesis.errors; namely AbnormalExit, BadData, BadTemplateDraw, DefinitelyNoSuchExample, Timeout, and WrongFormat.
2019-02-01 12:50:30 +01:00
${PYSITELIB}/hypothesis/extra/django/_fields.py
${PYSITELIB}/hypothesis/extra/django/_fields.pyc
${PYSITELIB}/hypothesis/extra/django/_fields.pyo
${PYSITELIB}/hypothesis/extra/django/_impl.py
${PYSITELIB}/hypothesis/extra/django/_impl.pyc
${PYSITELIB}/hypothesis/extra/django/_impl.pyo
py-hypothesis: updated to 3.74.0 3.74.0: This release checks that the value of the :attr:~hypothesis.settings.print_blob setting is a :class:~hypothesis.PrintSettings instance. Being able to specify a boolean value was not intended, and is now deprecated. In addition, specifying True will now cause the blob to always be printed, instead of causing it to be suppressed. Specifying any value that is not a :class:~hypothesis.PrintSettings or a boolean is now an error. 3.73.5: Changes the documentation for hypothesis.strategies.datetimes, hypothesis.strategies.dates, hypothesis.strategies.times to use the new parameter names min_value and max_value instead of the deprecated names 3.73.4: This patch ensures that Hypothesis deprecation warnings display the code that emitted them when you're not running in -Werror mode (:issue:652). 3.73.3: Tracebacks involving :func:@composite <hypothesis.strategies.composite> are now slightly shorter due to some internal refactoring. 3.73.2: This patch fixes errors in the internal comments for one of the shrinker passes. There is no user-visible change. 3.73.1: This patch substantially improves the distribution of data generated with :func:~hypothesis.strategies.recursive, and fixes a rare internal error (:issue:1502). 3.73.0: This release adds the :func:~hypothesis.extra.dpcontracts.fulfill function, which is designed for testing code that uses :pypi:dpcontracts 0.4 or later for input validation. This provides some syntactic sugar around use of :func:~hypothesis.assume, to automatically filter out and retry calls that cause a precondition check to fail (:issue:1474). 3.72.0: This release makes setting attributes of the :class:hypothesis.settings class an explicit error. This has never had any effect, but could mislead users who confused it with the current settings instance hypothesis.settings.default (which is also immutable). You can change the global settings with :ref:settings profiles <settings_profiles>. 3.71.11: This patch factors out some common code in the shrinker for iterating over pairs of data blocks. There should be no user-visible change.
2018-10-03 11:56:52 +02:00
${PYSITELIB}/hypothesis/extra/dpcontracts.py
${PYSITELIB}/hypothesis/extra/dpcontracts.pyc
${PYSITELIB}/hypothesis/extra/dpcontracts.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/extra/ghostwriter.py
${PYSITELIB}/hypothesis/extra/ghostwriter.pyc
${PYSITELIB}/hypothesis/extra/ghostwriter.pyo
py-hypothesis: updated to 4.4.3 4.4.3: This release fixes an open file leak that used to cause ResourceWarnings. 4.4.2: This release changes Hypothesis's internal approach to caching the results of executing test cases. The result should be that it is now significantly less memory hungry, especially when shrinking large test cases. Some tests may get slower or faster depending on whether the new or old caching strategy was well suited to them, but any change in speed in either direction should be minor. 4.4.1: This patch tightens up some of our internal heuristics to deal with shrinking floating point numbers, which will now run in fewer circumstances. You are fairly unlikely to see much difference from this, but if you do you are likely to see shrinking become slightly faster and/or producing slightly worse results. 4.4.0: This release adds the :func:~hypothesis.extra.django.from_form function, which allows automatic testing against Django forms. (:issue:35) 4.3.0: This release deprecates HealthCheck.hung_test and disables the associated runtime check for tests that ran for more than five minutes. Such a check is redundant now that we enforce the deadline and max_examples setting, which can be adjusted independently. 4.2.0: This release adds a new module, hypothesis.extra.lark, which you can use to generate strings matching a context-free grammar. In this initial version, only :pypi:lark-parser EBNF grammars are supported, by the new :func:hypothesis.extra.lark.from_lark function. 4.1.2: This patch fixes a very rare overflow bug (:issue:1748) which could raise an InvalidArgument error in :func:~hypothesis.strategies.complex_numbers even though the arguments were valid. 4.1.1: This release makes some improvements to internal code organisation and documentation and has no impact on behaviour. 4.1.0: This release adds :func:~hypothesis.register_random, which registers random.Random instances or compatible objects to be seeded and reset by Hypothesis to ensure that test cases are deterministic. We still recommend explicitly passing a random.Random instance from :func:~hypothesis.strategies.randoms if possible, but registering a framework-global state for Hypothesis to manage is better than flaky tests! 4.0.2: This patch fixes :issue:1387, where bounded :func:~hypothesis.strategies.integers with a very large range would almost always generate very large numbers. Now, we usually use the same tuned distribution as unbounded :func:~hypothesis.strategies.integers. 4.0.1: This release randomizes the order in which the shrinker tries some of its initial normalization operations. You are unlikely to see much difference as a result unless your generated examples are very large. In this case you may see some performance improvements in shrinking. 4.0.0: Welcome to the next major version of Hypothesis! There are no new features here, as we release those in minor versions. Instead, 4.0 is a chance for us to remove deprecated features (many already converted into no-ops), and turn a variety of warnings into errors. If you were running on the last version of Hypothesis 3.x without any Hypothesis deprecation warnings (or using private APIs), this will be a very boring upgrade. In fact, nothing will change for you at all. Per :ref:our deprecation policy <deprecation-policy>, warnings added in the last six months (after 2018-07-05) have not been converted to errors. Removals hypothesis.extra.datetime has been removed, replaced by the core date and time strategies. hypothesis.extra.fakefactory has been removed, replaced by general expansion of Hypothesis' strategies and the third-party ecosystem. The SQLite example database backend has been removed. Settings The :obj:~hypothesis.settings.deadline is now enforced by default, rather than just emitting a warning when the default (200 milliseconds per test case) deadline is exceeded. The database_file setting has been removed; use :obj:~hypothesis.settings.database. The perform_health_check setting has been removed; use :obj:~hypothesis.settings.suppress_health_check. The max_shrinks setting has been removed; use :obj:~hypothesis.settings.phases to disable shrinking. The min_satisfying_examples, max_iterations, strict, timeout, and use_coverage settings have been removed without user-configurable replacements. Strategies The elements argument is now required for collection strategies. The average_size argument was a no-op and has been removed. Date and time strategies now only accept min_value and max_value for bounds. :func:~hypothesis.strategies.builds now requires that the thing to build is passed as the first positional argument. Alphabet validation for :func:~hypothesis.strategies.text raises errors, not warnings, as does category validation for :func:~hypothesis.strategies.characters. The choices() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data with :func:~hypothesis.strategies.sampled_from, so choice(elements) becomes data.draw(sampled_from(elements)). The streaming() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data and replace iterating over the stream with data.draw() calls. :func:~hypothesis.strategies.sampled_from and :func:~hypothesis.strategies.permutations raise errors instead of warnings if passed a collection that is not a sequence. Miscellaneous Applying :func:@given <hypothesis.given> to a test function multiple times was really inefficient, and now it's also an error. Using the .example() method of a strategy (intended for interactive exploration) within another strategy or a test function always weakened data generation and broke shrinking, and now it's an error too. The HYPOTHESIS_DATABASE_FILE environment variable is no longer supported, as the database_file setting has been removed. The HYPOTHESIS_VERBOSITY_LEVEL environment variable is no longer supported. You can use the --hypothesis-verbosity pytest argument instead, or write your own setup code using the settings profile system to replace it. Using :func:@seed <hypothesis.seed> or :obj:derandomize=True <hypothesis.settings.derandomize> now forces :obj:database=None <hypothesis.settings.database> to ensure results are in fact reproducible. If :obj:~hypothesis.settings.database is not None, doing so also emits a HypothesisWarning. Unused exception types have been removed from hypothesis.errors; namely AbnormalExit, BadData, BadTemplateDraw, DefinitelyNoSuchExample, Timeout, and WrongFormat.
2019-02-01 12:50:30 +01:00
${PYSITELIB}/hypothesis/extra/lark.py
${PYSITELIB}/hypothesis/extra/lark.pyc
${PYSITELIB}/hypothesis/extra/lark.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/extra/numpy.py
${PYSITELIB}/hypothesis/extra/numpy.pyc
${PYSITELIB}/hypothesis/extra/numpy.pyo
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-30 15:12:04 +02:00
${PYSITELIB}/hypothesis/extra/pandas/__init__.py
${PYSITELIB}/hypothesis/extra/pandas/__init__.pyc
${PYSITELIB}/hypothesis/extra/pandas/__init__.pyo
${PYSITELIB}/hypothesis/extra/pandas/impl.py
${PYSITELIB}/hypothesis/extra/pandas/impl.pyc
${PYSITELIB}/hypothesis/extra/pandas/impl.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/extra/pytestplugin.py
${PYSITELIB}/hypothesis/extra/pytestplugin.pyc
${PYSITELIB}/hypothesis/extra/pytestplugin.pyo
Changes 3.11.0: This is a feature release, adding datetime-related strategies to the core strategies. extra.pytz.timezones allows you to sample pytz timezones from the Olsen database. Use directly in a recipe for tz-aware datetimes, or compose with st.none() to allow a mix of aware and naive output. The new dates, times, datetimes, and timedeltas strategies in hypothesis.strategies are all constrained by objects of their type. This means that you can generate dates bounded by a single day (i.e. a single date), or datetimes constrained to the microsecond. times and datetimes take an optional timezones= argument, which defaults to none() for naive times. You can use our extra strategy based on pytz, or roll your own timezones strategy with dateutil or even the standard library. The old dates, times, and datetimes strategies in hypothesis.extra.datetimes are deprecated in favor of the new core strategies, which are more flexible and have no dependencies.
2017-05-24 13:28:37 +02:00
${PYSITELIB}/hypothesis/extra/pytz.py
${PYSITELIB}/hypothesis/extra/pytz.pyc
${PYSITELIB}/hypothesis/extra/pytz.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/extra/redis.py
${PYSITELIB}/hypothesis/extra/redis.pyc
${PYSITELIB}/hypothesis/extra/redis.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/__init__.py
${PYSITELIB}/hypothesis/internal/__init__.pyc
${PYSITELIB}/hypothesis/internal/__init__.pyo
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-30 15:12:04 +02:00
${PYSITELIB}/hypothesis/internal/cache.py
${PYSITELIB}/hypothesis/internal/cache.pyc
${PYSITELIB}/hypothesis/internal/cache.pyo
py-hypothesis: updated to 3.55.0 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. 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. 3.53.0: This release removes support for Django 1.8, which reached end of life on 2018-04-01.
2018-04-05 14:43:27 +02:00
${PYSITELIB}/hypothesis/internal/cathetus.py
${PYSITELIB}/hypothesis/internal/cathetus.pyc
${PYSITELIB}/hypothesis/internal/cathetus.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/charmap.py
${PYSITELIB}/hypothesis/internal/charmap.pyc
${PYSITELIB}/hypothesis/internal/charmap.pyo
${PYSITELIB}/hypothesis/internal/compat.py
${PYSITELIB}/hypothesis/internal/compat.pyc
${PYSITELIB}/hypothesis/internal/compat.pyo
${PYSITELIB}/hypothesis/internal/conjecture/__init__.py
${PYSITELIB}/hypothesis/internal/conjecture/__init__.pyc
${PYSITELIB}/hypothesis/internal/conjecture/__init__.pyo
py-hypothesis: updated to 4.33.1 4.33.1: This patch works around a crash when an incompatible version of Numpy is installed under PyPy 5.10 (Python 2.7). If you are still using Python 2, please upgrade to Python 3 as soon as possible - it will be unsupported at the end of this year. 4.33.0: This release improves the :func:~hypothesis.provisional.domains strategy, as well as the :func:~hypothesis.provisional.urls and the :func:~hypothesis.strategies.emails strategies which use it. These strategies now use the full IANA list of Top Level Domains and are correct as per :rfc:1035. Passing tests using these strategies may now fail. 4.32.3: This patch tidies up the repr of several settings-related objects, at runtime and in the documentation, and deprecates the undocumented edge case that phases=None was treated like phases=tuple(Phase). It *also* fixes :func:~hypothesis.extra.lark.from_lark with :pypi:lark 0.7.2 <lark-parser> and later. 4.32.2: This patch updates some internal comments for :pypi:mypy 0.720. There is no user-visible impact. 4.32.1: This release changes how the shrinker represents its progress internally. For large generated test cases this should result in significantly less memory usage and possibly faster shrinking. Small generated test cases may be slightly slower to shrink but this shouldn't be very noticeable. 4.32.0: This release makes :func:~hypothesis.extra.numpy.arrays more pedantic about elements strategies that cannot be exactly represented as array elements. In practice, you will see new warnings if you were using a float16 or float32 dtype without passing :func:~hypothesis.strategies.floats the width=16 or width=32 arguments respectively. The previous behaviour could lead to silent truncation, and thus some elements being equal to an explicitly excluded bound (:issue:1899). 4.31.1: This patch changes an internal use of MD5 to SHA hashes, to better support users subject to FIPS-140. There is no user-visible or API change. 4.31.0: This release simplifies the logic of the :attr:~hypothesis.settings.print_blob setting by removing the option to set it to PrintSettings.INFER. As a result the print_blob setting now takes a single boolean value, and the use of PrintSettings is deprecated. 4.28.2: This patch improves the docstrings of several Hypothesis strategies, by clarifying markup and adding cross-references. There is no runtime change. 4.28.1: This patch improves the behaviour of the :func:~hypothesis.strategies.text strategy when passed an alphabet which is not a strategy. The value is now interpreted as whitelist_characters to :func:~hypothesis.strategies.characters instead of a sequence for :func:~hypothesis.strategies.sampled_from, which standardises the distribution of examples and the shrinking behaviour. You can get the previous behaviour by using lists(sampled_from(alphabet)).map("".map) instead. 4.28.0: This release deprecates find(). The .example() method is a better replacement if you want *an* example, and for the rare occasions where you want the *minimal* example you can get it from :func:@given <hypothesis.given>. :func:@given <hypothesis.given> has steadily outstripped find() in both features and performance over recent years, and as we do not have the resources to maintain and test both we think it is better to focus on just one. 4.27.0: This release refactors the implementation of the .example() method, to more accurately represent the data which will be generated by :func:@given <hypothesis.given>. As a result, calling s.example() on an empty strategy s (such as :func:~hypothesis.strategies.nothing) now raises Unsatisfiable instead of the old NoExamples exception. 4.26.4: This patch ensures that the Pandas extra will keep working when Python 3.8 removes abstract base classes from the top-level :obj:python:collections namespace. This also fixes the relevant warning in Python 3.7, but there is no other difference in behaviour and you do not need to do anything. 4.26.3: This release fixes :issue:2027, by changing the way Hypothesis tries to generate distinct examples to be more efficient. This may result in slightly different data distribution, and should improve generation performance in general, but should otherwise have minimal user impact. 4.26.2: This release fixes :issue:1864, where some simple tests would perform very slowly, because they would run many times with each subsequent run being progressively slower. They will now stop after a more reasonable number of runs without hitting this problem. Unless you are hitting exactly this issue, it is unlikely that this release will have any effect, but certain classes of custom generators that are currently very slow may become a bit faster, or start to trigger health check failures. 4.26.1: This release adds the strategy :func:~hypothesis.extra.numpy.integer_array_indices, which generates tuples of Numpy arrays that can be used for advanced indexing <http://www.pythonlikeyoumeanit.com/Module3_IntroducingNumpy/AdvancedIndexing.html#Integer-Array-Indexing>_ to select an array of a specified shape. 4.26.0: This release significantly improves the performance of drawing unique collections whose elements are drawn from :func:~hypothesis.strategies.sampled_from strategies. As a side effect, this detects an error condition that would previously have passed silently: When the min_size argument on a collection with distinct elements is greater than the number of elements being sampled, this will now raise an error. 4.25.1: This release removes some defunct internal functionality that was only being used for testing. It should have no user visible impact. 4.25.0: This release deprecates and disables the buffer_size setting, which should have been treated as a private implementation detail all along. We recommend simply deleting this settings argument. 4.24.6: This patch makes :func:~hypothesis.strategies.datetimes more efficient, as it now handles short months correctly by construction instead of filtering. 4.24.5: This patch improves the development experience by simplifying the tracebacks you will see when e.g. you have used the .map(...) method of a strategy and the mapped function raises an exception. No new exceptions can be raised, nor existing exceptions change anything but their traceback. We're simply using if-statements rather than exceptions for control flow in a certain part of the internals! 4.24.4: This patch fixes :issue:2014, where our compatibility layer broke with version 3.7.4 of the :pypi:typing module backport on PyPI. This issue only affects Python 2. We remind users that Hypothesis, like many other packages, will drop Python 2 support on 2020-01-01 <https://python3statement.org>__ and already has several features that are only available on Python 3. 4.24.3: This patch improves the implementation of an internal wrapper on Python 3.8 beta1 (and will break on the alphas; but they're not meant to be stable). On other versions, there is no change at all.
2019-08-22 13:05:27 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/choicetree.py
${PYSITELIB}/hypothesis/internal/conjecture/choicetree.pyc
${PYSITELIB}/hypothesis/internal/conjecture/choicetree.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/data.py
${PYSITELIB}/hypothesis/internal/conjecture/data.pyc
${PYSITELIB}/hypothesis/internal/conjecture/data.pyo
py-hypothesis: updated to 4.4.3 4.4.3: This release fixes an open file leak that used to cause ResourceWarnings. 4.4.2: This release changes Hypothesis's internal approach to caching the results of executing test cases. The result should be that it is now significantly less memory hungry, especially when shrinking large test cases. Some tests may get slower or faster depending on whether the new or old caching strategy was well suited to them, but any change in speed in either direction should be minor. 4.4.1: This patch tightens up some of our internal heuristics to deal with shrinking floating point numbers, which will now run in fewer circumstances. You are fairly unlikely to see much difference from this, but if you do you are likely to see shrinking become slightly faster and/or producing slightly worse results. 4.4.0: This release adds the :func:~hypothesis.extra.django.from_form function, which allows automatic testing against Django forms. (:issue:35) 4.3.0: This release deprecates HealthCheck.hung_test and disables the associated runtime check for tests that ran for more than five minutes. Such a check is redundant now that we enforce the deadline and max_examples setting, which can be adjusted independently. 4.2.0: This release adds a new module, hypothesis.extra.lark, which you can use to generate strings matching a context-free grammar. In this initial version, only :pypi:lark-parser EBNF grammars are supported, by the new :func:hypothesis.extra.lark.from_lark function. 4.1.2: This patch fixes a very rare overflow bug (:issue:1748) which could raise an InvalidArgument error in :func:~hypothesis.strategies.complex_numbers even though the arguments were valid. 4.1.1: This release makes some improvements to internal code organisation and documentation and has no impact on behaviour. 4.1.0: This release adds :func:~hypothesis.register_random, which registers random.Random instances or compatible objects to be seeded and reset by Hypothesis to ensure that test cases are deterministic. We still recommend explicitly passing a random.Random instance from :func:~hypothesis.strategies.randoms if possible, but registering a framework-global state for Hypothesis to manage is better than flaky tests! 4.0.2: This patch fixes :issue:1387, where bounded :func:~hypothesis.strategies.integers with a very large range would almost always generate very large numbers. Now, we usually use the same tuned distribution as unbounded :func:~hypothesis.strategies.integers. 4.0.1: This release randomizes the order in which the shrinker tries some of its initial normalization operations. You are unlikely to see much difference as a result unless your generated examples are very large. In this case you may see some performance improvements in shrinking. 4.0.0: Welcome to the next major version of Hypothesis! There are no new features here, as we release those in minor versions. Instead, 4.0 is a chance for us to remove deprecated features (many already converted into no-ops), and turn a variety of warnings into errors. If you were running on the last version of Hypothesis 3.x without any Hypothesis deprecation warnings (or using private APIs), this will be a very boring upgrade. In fact, nothing will change for you at all. Per :ref:our deprecation policy <deprecation-policy>, warnings added in the last six months (after 2018-07-05) have not been converted to errors. Removals hypothesis.extra.datetime has been removed, replaced by the core date and time strategies. hypothesis.extra.fakefactory has been removed, replaced by general expansion of Hypothesis' strategies and the third-party ecosystem. The SQLite example database backend has been removed. Settings The :obj:~hypothesis.settings.deadline is now enforced by default, rather than just emitting a warning when the default (200 milliseconds per test case) deadline is exceeded. The database_file setting has been removed; use :obj:~hypothesis.settings.database. The perform_health_check setting has been removed; use :obj:~hypothesis.settings.suppress_health_check. The max_shrinks setting has been removed; use :obj:~hypothesis.settings.phases to disable shrinking. The min_satisfying_examples, max_iterations, strict, timeout, and use_coverage settings have been removed without user-configurable replacements. Strategies The elements argument is now required for collection strategies. The average_size argument was a no-op and has been removed. Date and time strategies now only accept min_value and max_value for bounds. :func:~hypothesis.strategies.builds now requires that the thing to build is passed as the first positional argument. Alphabet validation for :func:~hypothesis.strategies.text raises errors, not warnings, as does category validation for :func:~hypothesis.strategies.characters. The choices() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data with :func:~hypothesis.strategies.sampled_from, so choice(elements) becomes data.draw(sampled_from(elements)). The streaming() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data and replace iterating over the stream with data.draw() calls. :func:~hypothesis.strategies.sampled_from and :func:~hypothesis.strategies.permutations raise errors instead of warnings if passed a collection that is not a sequence. Miscellaneous Applying :func:@given <hypothesis.given> to a test function multiple times was really inefficient, and now it's also an error. Using the .example() method of a strategy (intended for interactive exploration) within another strategy or a test function always weakened data generation and broke shrinking, and now it's an error too. The HYPOTHESIS_DATABASE_FILE environment variable is no longer supported, as the database_file setting has been removed. The HYPOTHESIS_VERBOSITY_LEVEL environment variable is no longer supported. You can use the --hypothesis-verbosity pytest argument instead, or write your own setup code using the settings profile system to replace it. Using :func:@seed <hypothesis.seed> or :obj:derandomize=True <hypothesis.settings.derandomize> now forces :obj:database=None <hypothesis.settings.database> to ensure results are in fact reproducible. If :obj:~hypothesis.settings.database is not None, doing so also emits a HypothesisWarning. Unused exception types have been removed from hypothesis.errors; namely AbnormalExit, BadData, BadTemplateDraw, DefinitelyNoSuchExample, Timeout, and WrongFormat.
2019-02-01 12:50:30 +01:00
${PYSITELIB}/hypothesis/internal/conjecture/datatree.py
${PYSITELIB}/hypothesis/internal/conjecture/datatree.pyc
${PYSITELIB}/hypothesis/internal/conjecture/datatree.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/dfa/__init__.py
${PYSITELIB}/hypothesis/internal/conjecture/dfa/__init__.pyc
${PYSITELIB}/hypothesis/internal/conjecture/dfa/__init__.pyo
${PYSITELIB}/hypothesis/internal/conjecture/dfa/lstar.py
${PYSITELIB}/hypothesis/internal/conjecture/dfa/lstar.pyc
${PYSITELIB}/hypothesis/internal/conjecture/dfa/lstar.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/engine.py
${PYSITELIB}/hypothesis/internal/conjecture/engine.pyc
${PYSITELIB}/hypothesis/internal/conjecture/engine.pyo
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-08 13:03:28 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/floats.py
${PYSITELIB}/hypothesis/internal/conjecture/floats.pyc
${PYSITELIB}/hypothesis/internal/conjecture/floats.pyo
py-hypothesis: updated to 4.7.17 4.7.17: This release makes some micro-optimisations within Hypothesis's internal representation of test cases. This should cause heavily nested test cases to allocate less during generation and shrinking, which should speed things up slightly. 4.7.16: This changes the order in which Hypothesis runs certain operations during shrinking. This should significantly decrease memory usage and speed up shrinking of large examples. 4.7.15: This release allows Hypothesis to calculate a number of attributes of generated test cases lazily. This should significantly reduce memory usage and modestly improve performance, especially for large test cases. 4.7.14: This release reduces the number of operations the shrinker will try when reordering parts of a test case. This should in some circumstances significantly speed up shrinking. It may result in different final test cases, and if so usually slightly worse ones, but it should not generally have much impact on the end result as the operations removed were typically useless. 4.7.13: This release changes how Hypothesis reorders examples within a test case during shrinking. This should make shrinking considerably faster. 4.7.12: This release slightly improves the shrinker's ability to replace parts of a test case with their minimal version, by allowing it to do so in bulk rather than one at a time. Where this is effective, shrinker performance should be modestly improved. 4.7.11: This release makes some micro-optimisations to common operations performed during shrinking. Shrinking should now be slightly faster, especially for large examples with relatively fast test functions. 4.7.10: This release is a purely internal refactoring of Hypothesis's API for representing test cases. There should be no user visible effect. 4.7.9: This release changes certain shrink passes to make them more efficient when they aren't making progress. 4.7.8: This patch removes some unused code, which makes the internals a bit easier to understand. There is no user-visible impact. 4.7.7: This release reduces the number of operations the shrinker will try when reordering parts of a test case. This should in some circumstances significantly speed up shrinking. It may result in different final test cases, and if so usually slightly worse ones, but it should not generally have much impact on the end result as the operations removed were typically useless. 4.7.6: This patch removes some unused code from the shrinker. There is no user-visible change. 4.7.5: This release changes certain shrink passes to make them adaptive - that is, in cases where they are successfully making progress they may now do so significantly faster. 4.7.4: This is a docs-only patch, noting that because the :pypi:lark-parser is under active development at version 0.x, hypothesis[lark] APIs may break in minor releases if necessary to keep up with the upstream package. 4.7.3: This changes Hypothesis to no longer import various test frameworks by default (if they are installed). which will speed up the initial import hypothesis call. 4.7.2: This release changes Hypothesis's internal representation of a test case to calculate some expensive structural information on demand rather than eagerly. This should reduce memory usage a fair bit, and may make generation somewhat faster. 4.7.1: This release refactors the internal representation of previously run test cases. The main thing you should see as a result is that Hypothesis becomes somewhat less memory hungry. 4.7.0: This patch allows :func:~hypothesis.extra.numpy.array_shapes to generate shapes with side-length or even dimension zero, though the minimum still defaults to one. These shapes are rare and have some odd behavior, but are particularly important to test for just that reason! In a related bigfix, :func:~hypothesis.extra.numpy.arrays now supports generating zero-dimensional arrays with dtype=object and a strategy for iterable elements. Previously, the array element would incorrectly be set to the first item in the generated iterable.
2019-03-02 15:22:10 +01:00
${PYSITELIB}/hypothesis/internal/conjecture/junkdrawer.py
${PYSITELIB}/hypothesis/internal/conjecture/junkdrawer.pyc
${PYSITELIB}/hypothesis/internal/conjecture/junkdrawer.pyo
py-hypothesis: updated to 4.44.2 4.44.2: This release fixes :func:`@given <hypothesis.given>` to only complain about missing keyword-only arguments if the associated test function is actually called. This matches the behaviour of other InvalidArgument errors produced by @given. 4.44.1: This patch allows Hypothesis to run in environments that do not specify a __file__, such as a :mod:`python:zipapp` (:issue:`2196`). 4.44.0: This release adds a gufunc argument to :func:`~hypothesis.extra.numpy.mutually_broadcastable_shapes` (:issue:`2174`), which allows us to generate shapes which are valid for functions like :obj:`numpy:numpy.matmul` that require shapes which are not simply broadcastable. 4.43.9: This patch fixes :issue:`2108`, where the first test using :func:`~hypothesis.strategies.data` to draw from :func:`~hypothesis.strategies.characters` or :func:`~hypothesis.strategies.text` would be flaky due to unreliable test timings. Time taken by lazy instantiation of strategies is now counted towards drawing from the strategy, rather than towards the deadline for the test function. 4.43.8: This release ensures that the strategies passed to :func:`@given <hypothesis.given>` are properly validated when applied to a test method inside a test class. This should result in clearer error messages when some of those strategies are invalid. 4.43.7: This release changes how Hypothesis manages its search space in cases where it generates redundant data. This should cause it to generate significantly fewer duplicated examples (especially with short integer ranges), and may cause it to produce more useful examples in some cases (especially ones where there is a significant amount of filtering). 4.43.6: This patch refactors width handling in :func:`~hypothesis.strategies.floats`; you may notice small performance improvements but the main purpose is to enable work on :issue:`1704` (improving shrinking of bounded floats). 4.43.5: This patch removes an unused internal flag. There is no user-visible change. 4.43.4: This patch corrects the exception type and error message you get if you attempt to use :func:`~hypothesis.strategies.data` to draw from something which is not a strategy. This never worked, but the error is more helpful now. 4.43.3: We've adopted :pypi:`flake8-bugbear` to check for a few more style issues, and this patch implements the minor internal cleanups it suggested. There is no user-visible change. 4.43.2: This patch fixes the formatting of some documentation, but there is no change to any executed code. 4.43.1: Python 3.8's new :obj:`python:typing.Literal` type - see PEP 586 for details - is now supported in :func:`~hypothesis.strategies.from_type`. 4.43.0: This release adds the strategy :func:`~hypothesis.extra.numpy.mutually_broadcastable_shapes`, which generates multiple array shapes that are mutually broadcast-compatible with an optional user-specified base-shape. This is a generalisation of :func:`~hypothesis.extra.numpy.broadcastable_shapes`. It relies heavily on non-public internals for performance when generating and shrinking examples. We intend to support generating shapes matching a ufunc signature in a future version (:issue:`2174`). 4.42.10: This release fixes :func:`~hypothesis.strategies.from_type` when used with bounded or constrained :obj:`python:typing.TypeVar` objects (:issue:`2094`). Previously, distinct typevars with the same constraints would be treated as all single typevar, and in cases where a typevar bound was resolved to a union of subclasses this could result in mixed types being generated for that typevar. 4.42.9: This patch ensures that the default value :func:`~hypothesis.extra.numpy.broadcastable_shapes` chooses for max_dims is always valid (at most 32), even if you pass min_dims=32. 4.42.8: This patch ensures that we only add profile information to the pytest header if running either pytest or Hypothesis in verbose mode, matching the builtin cache plugin (:issue:`2155`). 4.42.7: This patch makes stateful step printing expand the result of a step into multiple variables when you return :func:`~hypothesis.stateful.multiple` (:issue:`2139`). 4.42.6: This release fixes a bug (:issue:`2166`) where a Unicode character info cache file was generated but never used on subsequent test runs, causing tests to run more slowly than they should have. 4.42.5: This patch corrects some internal documentation. There is no user-visible change. 4.42.4: This release fixes a bug (:issue:`2160`) where decorators applied after :func:`@settings <hypothesis.settings>` and before :func:`@given <hypothesis.given>` were ignored. 4.42.3: This release updates Hypothesis's formatting to the new version of :pypi:`black`, and has absolutely no user visible effect. 4.42.2: This release fixes a bug in :func:`~hypothesis.strategies.recursive` which would have meant that in practice max_leaves was treated as if it was lower than it actually is - specifically it would be capped at the largest power of two smaller than it. It is now handled correctly. 4.42.1: Python 3.8's new :class:`python:typing.SupportsIndex` type - see PEP 357 for details - is now supported in :func:`~hypothesis.strategies.from_type`. 4.42.0: This release significantly simplifies Hypothesis's internal logic for data generation, by removing a number of heuristics of questionable or unproven value. The results of this change will vary significantly from test to test. Most test suites will see significantly faster data generation and lower memory usage. The "quality" of the generated data may go up or down depending on your particular test suites. If you see any significant regressions in Hypothesis's ability to find bugs in your code as a result of this release, please file an issue to let us know. Users of the new :ref:`targeted property-based testing <targeted-search>` functionality are reasonably likely to see improvements in data generation, as this release changes the search algorithm for targeted property based testing to one that is more likely to be productive than the existing approach.
2019-11-13 22:08:30 +01:00
${PYSITELIB}/hypothesis/internal/conjecture/optimiser.py
${PYSITELIB}/hypothesis/internal/conjecture/optimiser.pyc
${PYSITELIB}/hypothesis/internal/conjecture/optimiser.pyo
py-hypothesis: updated to 4.57.1 4.57.1: This patch improves the type hints and documentation for the django extra. There is no runtime change. 4.57.0: This release improves support for the SupportsOp protocols from the typing module when using on from_type() as outlined in issue 2292. The following types now generate much more varied strategies when called with from_type(): typing.SupportsAbs typing.SupportsBytes typing.SupportsComplex typing.SupportsInt typing.SupportsFloat typing.SupportsRound Note that using from_type() with one of the above strategies will not ensure that the the specified function will execute successfully (ie : the strategy returned for from_type(typing.SupportsAbs) may include NaNs or things which cause the abs() function to error. ) 4.56.3: This release fixes a small internal bug in shrinking which could have caused it to perform slightly more tests than were necessary. Fixing this shouldn’t have much effect but it will make shrinking slightly faster. 4.56.2: This release removes an internal heuristic that was no longer providing much benefit. It is unlikely that there will be any user visible effect. 4.56.1: This release further improves the optimisation algorithm for targeted property-based testing. 4.56.0: This release enables deprecation warnings even when the verbosity setting is quiet, in preparation for Hypothesis 5.0. Warnings can still be filtered by the standard mechanisms provided in the standard-library warnings module. 4.55.4: This release improves Hypothesis’s management of the set of test cases it tracks between runs. It will only do anything if you have Phase.target enabled and an example database set. In those circumstances it should result in a more thorough and faster set of examples that are tried on each run. 4.55.3: This release makes Hypothesis better at generating test cases where generated values are duplicated in different parts of the test case. This will be especially noticeable with reasonably complex values, as it was already able to do this for simpler ones such as integers or floats. 4.55.2: This release expands the set of test cases that Hypothesis saves in its database for future runs to include a representative set of “structurally different” test cases - e.g. it might try to save test cases where a given list is empty or not. Currently this is unlikely to have much user visible impact except to produce slightly more consistent behaviour between consecutive runs of a test suite. It is mostly groundwork for future improvements which will exploit this functionality more effectively. 4.55.1: This patch fixes issue 2257, where from_type() could incorrectly generate bytestrings when passed a generic typing.Sequence such as Sequence[set]. 4.55.0: This release adds database support for targeted property-based testing, so the best examples based on the targeting will be saved and reused between runs. This is mostly laying groundwork for future features in this area, but will also make targeted property-based tests more useful during development, where the same tests tend to get run over and over again. If max_examples is large, this may increase memory usage significantly under some circumstances, but these should be relatively rare. This release also adds a dependency on the sortedcontainers package. 4.54.2: This release improves the optimisation algorithm for targeted property-based testing, so that it will find higher quality results more reliably. Specifically, in cases where it would previously have got near a local optimum, it will now tend to achieve the locally optimal value. 4.54.1: This release is mostly internal changes in support of better testing of the core engine. You are unlikely to see much effect, although some internal heuristics have changed slightly. 4.54.0: This release adds a dedicated phase for targeted property-based testing, and (somewhat) improves the targeting algorithm so that it will find higher quality results more reliably. This comes at a cost of making it more likely to get stuck in a local optimum.
2020-06-20 09:06:42 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/pareto.py
${PYSITELIB}/hypothesis/internal/conjecture/pareto.pyc
${PYSITELIB}/hypothesis/internal/conjecture/pareto.pyo
py-hypothesis: updated to 4.4.3 4.4.3: This release fixes an open file leak that used to cause ResourceWarnings. 4.4.2: This release changes Hypothesis's internal approach to caching the results of executing test cases. The result should be that it is now significantly less memory hungry, especially when shrinking large test cases. Some tests may get slower or faster depending on whether the new or old caching strategy was well suited to them, but any change in speed in either direction should be minor. 4.4.1: This patch tightens up some of our internal heuristics to deal with shrinking floating point numbers, which will now run in fewer circumstances. You are fairly unlikely to see much difference from this, but if you do you are likely to see shrinking become slightly faster and/or producing slightly worse results. 4.4.0: This release adds the :func:~hypothesis.extra.django.from_form function, which allows automatic testing against Django forms. (:issue:35) 4.3.0: This release deprecates HealthCheck.hung_test and disables the associated runtime check for tests that ran for more than five minutes. Such a check is redundant now that we enforce the deadline and max_examples setting, which can be adjusted independently. 4.2.0: This release adds a new module, hypothesis.extra.lark, which you can use to generate strings matching a context-free grammar. In this initial version, only :pypi:lark-parser EBNF grammars are supported, by the new :func:hypothesis.extra.lark.from_lark function. 4.1.2: This patch fixes a very rare overflow bug (:issue:1748) which could raise an InvalidArgument error in :func:~hypothesis.strategies.complex_numbers even though the arguments were valid. 4.1.1: This release makes some improvements to internal code organisation and documentation and has no impact on behaviour. 4.1.0: This release adds :func:~hypothesis.register_random, which registers random.Random instances or compatible objects to be seeded and reset by Hypothesis to ensure that test cases are deterministic. We still recommend explicitly passing a random.Random instance from :func:~hypothesis.strategies.randoms if possible, but registering a framework-global state for Hypothesis to manage is better than flaky tests! 4.0.2: This patch fixes :issue:1387, where bounded :func:~hypothesis.strategies.integers with a very large range would almost always generate very large numbers. Now, we usually use the same tuned distribution as unbounded :func:~hypothesis.strategies.integers. 4.0.1: This release randomizes the order in which the shrinker tries some of its initial normalization operations. You are unlikely to see much difference as a result unless your generated examples are very large. In this case you may see some performance improvements in shrinking. 4.0.0: Welcome to the next major version of Hypothesis! There are no new features here, as we release those in minor versions. Instead, 4.0 is a chance for us to remove deprecated features (many already converted into no-ops), and turn a variety of warnings into errors. If you were running on the last version of Hypothesis 3.x without any Hypothesis deprecation warnings (or using private APIs), this will be a very boring upgrade. In fact, nothing will change for you at all. Per :ref:our deprecation policy <deprecation-policy>, warnings added in the last six months (after 2018-07-05) have not been converted to errors. Removals hypothesis.extra.datetime has been removed, replaced by the core date and time strategies. hypothesis.extra.fakefactory has been removed, replaced by general expansion of Hypothesis' strategies and the third-party ecosystem. The SQLite example database backend has been removed. Settings The :obj:~hypothesis.settings.deadline is now enforced by default, rather than just emitting a warning when the default (200 milliseconds per test case) deadline is exceeded. The database_file setting has been removed; use :obj:~hypothesis.settings.database. The perform_health_check setting has been removed; use :obj:~hypothesis.settings.suppress_health_check. The max_shrinks setting has been removed; use :obj:~hypothesis.settings.phases to disable shrinking. The min_satisfying_examples, max_iterations, strict, timeout, and use_coverage settings have been removed without user-configurable replacements. Strategies The elements argument is now required for collection strategies. The average_size argument was a no-op and has been removed. Date and time strategies now only accept min_value and max_value for bounds. :func:~hypothesis.strategies.builds now requires that the thing to build is passed as the first positional argument. Alphabet validation for :func:~hypothesis.strategies.text raises errors, not warnings, as does category validation for :func:~hypothesis.strategies.characters. The choices() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data with :func:~hypothesis.strategies.sampled_from, so choice(elements) becomes data.draw(sampled_from(elements)). The streaming() strategy has been removed. Instead, you can use :func:~hypothesis.strategies.data and replace iterating over the stream with data.draw() calls. :func:~hypothesis.strategies.sampled_from and :func:~hypothesis.strategies.permutations raise errors instead of warnings if passed a collection that is not a sequence. Miscellaneous Applying :func:@given <hypothesis.given> to a test function multiple times was really inefficient, and now it's also an error. Using the .example() method of a strategy (intended for interactive exploration) within another strategy or a test function always weakened data generation and broke shrinking, and now it's an error too. The HYPOTHESIS_DATABASE_FILE environment variable is no longer supported, as the database_file setting has been removed. The HYPOTHESIS_VERBOSITY_LEVEL environment variable is no longer supported. You can use the --hypothesis-verbosity pytest argument instead, or write your own setup code using the settings profile system to replace it. Using :func:@seed <hypothesis.seed> or :obj:derandomize=True <hypothesis.settings.derandomize> now forces :obj:database=None <hypothesis.settings.database> to ensure results are in fact reproducible. If :obj:~hypothesis.settings.database is not None, doing so also emits a HypothesisWarning. Unused exception types have been removed from hypothesis.errors; namely AbnormalExit, BadData, BadTemplateDraw, DefinitelyNoSuchExample, Timeout, and WrongFormat.
2019-02-01 12:50:30 +01:00
${PYSITELIB}/hypothesis/internal/conjecture/shrinker.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinker.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinker.pyo
py-hypothesis: updated to 3.68.0 3.68.0: :func:~hypothesis.extra.numpy.arrays now checks that integer and float values drawn from elements and fill strategies can be safely cast to the dtype of the array, and emits a warning otherwise. Elements in the resulting array could previously violate constraints on the elements strategy due to floating-point overflow or truncation of integers to fit smaller types. 3.67.1: This release contains a tiny refactoring of the internals. There is no user-visible change. 3.67.0: This release adds a width argument to :func:~hypothesis.strategies.floats, to generate lower-precision floating point numbers for e.g. Numpy arrays. The generated examples are always instances of Python's native float type, which is 64bit, but passing width=32 will ensure that all values can be exactly represented as 32bit floats. This can be useful to avoid overflow (to +/- infinity), and for efficiency of generation and shrinking. Half-precision floats (width=16) are also supported, but require Numpy if you are running Python 3.5 or earlier.
2018-08-17 09:15:22 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/__init__.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/__init__.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/__init__.pyo
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/common.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/common.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/common.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/dfas.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/dfas.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/dfas.pyo
py-hypothesis: updated to 3.68.0 3.68.0: :func:~hypothesis.extra.numpy.arrays now checks that integer and float values drawn from elements and fill strategies can be safely cast to the dtype of the array, and emits a warning otherwise. Elements in the resulting array could previously violate constraints on the elements strategy due to floating-point overflow or truncation of integers to fit smaller types. 3.67.1: This release contains a tiny refactoring of the internals. There is no user-visible change. 3.67.0: This release adds a width argument to :func:~hypothesis.strategies.floats, to generate lower-precision floating point numbers for e.g. Numpy arrays. The generated examples are always instances of Python's native float type, which is 64bit, but passing width=32 will ensure that all values can be exactly represented as 32bit floats. This can be useful to avoid overflow (to +/- infinity), and for efficiency of generation and shrinking. Half-precision floats (width=16) are also supported, but require Numpy if you are running Python 3.5 or earlier.
2018-08-17 09:15:22 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/floats.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/floats.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/floats.pyo
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/integer.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/integer.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/integer.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/learned_dfas.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/learned_dfas.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/learned_dfas.pyo
py-hypothesis: updated to 3.68.0 3.68.0: :func:~hypothesis.extra.numpy.arrays now checks that integer and float values drawn from elements and fill strategies can be safely cast to the dtype of the array, and emits a warning otherwise. Elements in the resulting array could previously violate constraints on the elements strategy due to floating-point overflow or truncation of integers to fit smaller types. 3.67.1: This release contains a tiny refactoring of the internals. There is no user-visible change. 3.67.0: This release adds a width argument to :func:~hypothesis.strategies.floats, to generate lower-precision floating point numbers for e.g. Numpy arrays. The generated examples are always instances of Python's native float type, which is 64bit, but passing width=32 will ensure that all values can be exactly represented as 32bit floats. This can be useful to avoid overflow (to +/- infinity), and for efficiency of generation and shrinking. Half-precision floats (width=16) are also supported, but require Numpy if you are running Python 3.5 or earlier.
2018-08-17 09:15:22 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/lexical.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/lexical.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/lexical.pyo
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/ordering.py
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/ordering.pyc
${PYSITELIB}/hypothesis/internal/conjecture/shrinking/ordering.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/conjecture/utils.py
${PYSITELIB}/hypothesis/internal/conjecture/utils.pyc
${PYSITELIB}/hypothesis/internal/conjecture/utils.pyo
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-30 15:12:04 +02:00
${PYSITELIB}/hypothesis/internal/coverage.py
${PYSITELIB}/hypothesis/internal/coverage.pyc
${PYSITELIB}/hypothesis/internal/coverage.pyo
Updated py-hypothesis to 3.5.3. 3.5.3 - 2016-10-05 This is a bug fix release. Bugs fixed: If the same test was running concurrently in two processes and there were examples already in the test database which no longer failed, Hypothesis would sometimes fail with a FileNotFoundError (IOError on Python 2) because an example it was trying to read was deleted before it was read. (Issue #372). Drawing from an integers() strategy with both a min_value and a max_value would reject too many examples needlessly. Now it repeatedly redraws until satisfied. (Pull request #366. Thanks to Calen Pennington for the contribution). 3.5.2 - 2016-09-24 This is a bug fix release. The Hypothesis pytest plugin broke pytest support for doctests. Now it doesn’t. 3.5.1 - 2016-09-23 This is a bug fix release. Hypothesis now runs cleanly in -B and -BB modes, avoiding mixing bytes and unicode. unittest.TestCase tests would now have shown up in the new statistics mode. Now they do. Similarly, stateful tests would not have shown up in statistics and now they do. Statistics now print with pytest node IDs (the names you’d get in pytest verbose mode). 3.5.0 - 2016-09-22 This is a feature release. fractions() and decimals() strategies now support min_value and max_value parameters. Thanks go to Anne Mulhern for the development of this feature. The Hypothesis pytest plugin now supports a –hypothesis-show-statistics parameter that gives detailed statistics about the tests that were run. Huge thanks to Jean-Louis Fuchs and Adfinis-SyGroup for funding the development of this feature. There is a new event() function that can be used to add custom statistics. Additionally there have been some minor bug fixes: In some cases Hypothesis should produce fewer duplicate examples (this will mostly only affect cases with a single parameter). py.test command line parameters are now under an option group for Hypothesis (thanks to David Keijser for fixing this) Hypothesis would previously error if you used function annotations on your tests under Python 3.4. The repr of many strategies using lambdas has been improved to include the lambda body (this was previously supported in many but not all cases).
2016-10-19 14:42:56 +02:00
${PYSITELIB}/hypothesis/internal/detection.py
${PYSITELIB}/hypothesis/internal/detection.pyc
${PYSITELIB}/hypothesis/internal/detection.pyo
py-hypothesis: updated to 3.65.0 3.65.0: This release deprecates the :obj:~hypothesis.settings.max_shrinks setting in favor of an internal heuristic. If you need to avoid shrinking examples, use the :obj:~hypothesis.settings.phases setting instead. (:issue:1235) 3.64.2: This release fixes a bug where an internal assertion error could sometimes be triggered while shrinking a failing test. 3.64.1: This patch fixes type-checking errors in our vendored pretty-printer, which were ignored by our mypy config but visible for anyone else (whoops). Thanks to Pi Delport for reporting :issue:1359 so promptly. 3.64.0: This release adds :ref:an interface <custom-function-execution> which can be used to insert a wrapper between the original test function and :func:@given <hypothesis.given> (:issue:1257). This will be particularly useful for test runner extensions such as :pypi:pytest-trio, but is not recommended for direct use by other users of Hypothesis. 3.63.0: This release adds a new mechanism to infer strategies for classes defined using :pypi:attrs, based on the the type, converter, or validator of each attribute. This inference is now built in to :func:~hypothesis.strategies.builds and :func:~hypothesis.strategies.from_type. On Python 2, :func:~hypothesis.strategies.from_type no longer generates instances of int when passed long, or vice-versa. 3.62.0: This release adds PEP 484 type hints to Hypothesis on a provisional basis, using the comment-based syntax for Python 2 compatibility. You can :ref:read more about our type hints here <our-type-hints>. It also adds the py.typed marker specified in PEP 561. After you pip install hypothesis, :pypi:mypy 0.590 or later will therefore type-check your use of our public interface! 3.61.0: This release deprecates the use of :class:~hypothesis.settings as a context manager, the use of which is somewhat ambiguous. Users should define settings with global state or with the :func:@settings(...) <hypothesis.settings> decorator. 3.60.1: Fixed a bug in generating an instance of a Django model from a strategy where the primary key is generated as part of the strategy. See :ref:details here <django-generating-primary-key>. 3.60.0: This release add initialize decorator for stateful testing (originally discussed in :issue:1216). initialize act as a special rule that is only called once, and all initialize rules are guaranteed to be called before any normal rule is called.
2018-07-03 09:47:45 +02:00
${PYSITELIB}/hypothesis/internal/entropy.py
${PYSITELIB}/hypothesis/internal/entropy.pyc
${PYSITELIB}/hypothesis/internal/entropy.pyo
Updated py-hypothesis to 3.8.2. 3.8.2 - 2017-04-26 This is a code reorganisation release that moves some internal test helpers out of the main source tree so as to not have changes to them trigger releases in future. 3.8.1 - 2017-04-26 This is a documentation release. Almost all code examples are now doctests checked in CI, eliminating stale examples. 3.8.0 - 2017-04-23 This is a feature release, adding the iterables strategy, equivalent to lists(...).map(iter) but with a much more useful repr. You can use this strategy to check that code doesn’t accidentally depend on sequence properties such as indexing support or repeated iteration. 3.7.4 - 2017-04-22 This is a bug fix release for a single bug: In 3.7.3, using @example and a pytest fixture in the same test could cause the test to fail to fill the arguments, and throw a TypeError. 3.7.3 - 2017-04-21 This release should include no user visible changes and is purely a refactoring release. This modularises the behaviour of the core “given” function, breaking it up into smaller and more accessible parts, but its actual behaviour should remain unchanged. 3.7.2 - 2017-04-21 This reverts an undocumented change in 3.7.1 which broke installation on debian stable: The specifier for the hypothesis[django] extra_requires had introduced a wild card, which was not supported on the default version of pip. 3.7.1 - 2017-04-21 This is a bug fix and internal improvements release. In particular Hypothesis now tracks a tree of where it has already explored. This allows it to avoid some classes of duplicate examples, and significantly improves the performance of shrinking failing examples by allowing it to skip some shrinks that it can determine can’t possibly work. Hypothesis will no longer seed the global random arbitrarily unless you have asked it to using random_module() Shrinking would previously have not worked correctly in some special cases on Python 2, and would have resulted in suboptimal examples.
2017-04-27 14:55:54 +02:00
${PYSITELIB}/hypothesis/internal/escalation.py
${PYSITELIB}/hypothesis/internal/escalation.pyc
${PYSITELIB}/hypothesis/internal/escalation.pyo
py-hypothesis: update to 6.8.1. 6.8.1 - 2021-03-14 This patch lays more groundwork for filter rewriting (issue #2701). There is no user-visible change… yet. 6.8.0 - 2021-03-11 This release registers the remaining builtin types, and teaches from_type() to try resolving ForwardRef and Type references to built-in types. 6.7.0 - 2021-03-10 This release teaches RuleBasedStateMachine to avoid checking invariant()s until all initialize() rules have been run. You can enable checking of specific invariants for incompletely initialized machines by using @invariant(check_during_init=True) (issue #2868). In previous versions, it was possible if awkward to implement this behaviour using precondition() and an auxiliary variable. 6.6.1 - 2021-03-09 This patch improves the error message when from_type() fails to resolve a forward-reference inside a typing.Type such as Type["int"] (issue #2565). 6.6.0 - 2021-03-07 This release makes it an explicit error to apply invariant() to a rule() or initialize() rule in stateful testing. Such a combination had unclear semantics, especially in combination with precondition(), and was never meant to be allowed (issue #2681). 6.5.0 - 2021-03-07 This release adds the explain phase, in which Hypothesis attempts to explain why your test failed by pointing to suspicious lines of code (i.e. those which were always, and only, run on failing inputs). We plan to include “generalising” failing examples in this phase in a future release (issue #2192). 6.4.3 - 2021-03-04 This patch fixes issue #2794, where nesting deferred() strategies within recursive() strategies could trigger an internal assertion. While it was always possible to get the same results from a more sensible strategy, the convoluted form now works too. 6.4.2 - 2021-03-04 This patch fixes several problems with mypy when –no-implicit-reexport was activated in user projects. Thanks to Nikita Sobolev for fixing issue #2884! 6.4.1 - 2021-03-04 This patch fixes an exception that occurs when using type unions of the typing_extensions Literal backport on Python 3.6. Thanks to Ben Anhalt for identifying and fixing this bug. 6.4.0 - 2021-03-02 This release fixes stateful testing methods with multiple precondition() decorators. Previously, only the outer-most precondition was checked (issue #2681). 6.3.4 - 2021-02-28 This patch refactors some internals of RuleBasedStateMachine. There is no change to the public API or behaviour. 6.3.3 - 2021-02-26 This patch moves some internal code, so that future work can avoid creating import cycles. There is no user-visible change. 6.3.2 - 2021-02-25 This patch enables register_type_strategy() for subclasses of typing.TypedDict. Previously, from_type() would ignore the registered strategy (issue #2872). Thanks to Ilya Lebedev for identifying and fixing this bug! 6.3.1 - 2021-02-24 This release lays the groundwork for automatic rewriting of simple filters, for example converting integers().filter(lambda x: x > 9) to integers(min_value=10). Note that this is not supported yet, and we will continue to recommend writing the efficient form directly wherever possible - predicate rewriting is provided mainly for the benefit of downstream libraries which would otherwise have to implement it for themselves (e.g. pandera and icontract-hypothesis). See issue #2701 for details. 6.3.0 - 2021-02-20 The Hypothesis pytest plugin now requires pytest version 4.6 or later. If the plugin detects an earlier version of pytest, it will automatically deactivate itself. (4.6.x is the earliest pytest branch that still accepts community bugfixes.) Hypothesis-based tests should continue to work in earlier versions of pytest, but enhanced integrations provided by the plugin (such as --hypothesis-show-statistics and other command-line flags) will no longer be available in obsolete pytest versions.
2021-03-17 14:13:31 +01:00
${PYSITELIB}/hypothesis/internal/filtering.py
${PYSITELIB}/hypothesis/internal/filtering.pyc
${PYSITELIB}/hypothesis/internal/filtering.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/floats.py
${PYSITELIB}/hypothesis/internal/floats.pyc
${PYSITELIB}/hypothesis/internal/floats.pyo
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-12-13 09:17:10 +01:00
${PYSITELIB}/hypothesis/internal/healthcheck.py
${PYSITELIB}/hypothesis/internal/healthcheck.pyc
${PYSITELIB}/hypothesis/internal/healthcheck.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/intervalsets.py
${PYSITELIB}/hypothesis/internal/intervalsets.pyc
${PYSITELIB}/hypothesis/internal/intervalsets.pyo
3.13.0: This release has two major aspects to it: The first is the introduction of :func:`~hypothesis.strategies.deferred`, which allows more natural definition of recursive (including mutually recursive) strategies. The second is a number of engine changes designed to support this sort of strategy better. These should have a knock-on effect of also improving the performance of any existing strategies that currently generate a lot of data or involve heavy nesting by reducing their typical example size.
2017-07-17 09:05:34 +02:00
${PYSITELIB}/hypothesis/internal/lazyformat.py
${PYSITELIB}/hypothesis/internal/lazyformat.pyc
${PYSITELIB}/hypothesis/internal/lazyformat.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/internal/reflection.py
${PYSITELIB}/hypothesis/internal/reflection.pyc
${PYSITELIB}/hypothesis/internal/reflection.pyo
py-hypothesis: update to 6.8.1. 6.8.1 - 2021-03-14 This patch lays more groundwork for filter rewriting (issue #2701). There is no user-visible change… yet. 6.8.0 - 2021-03-11 This release registers the remaining builtin types, and teaches from_type() to try resolving ForwardRef and Type references to built-in types. 6.7.0 - 2021-03-10 This release teaches RuleBasedStateMachine to avoid checking invariant()s until all initialize() rules have been run. You can enable checking of specific invariants for incompletely initialized machines by using @invariant(check_during_init=True) (issue #2868). In previous versions, it was possible if awkward to implement this behaviour using precondition() and an auxiliary variable. 6.6.1 - 2021-03-09 This patch improves the error message when from_type() fails to resolve a forward-reference inside a typing.Type such as Type["int"] (issue #2565). 6.6.0 - 2021-03-07 This release makes it an explicit error to apply invariant() to a rule() or initialize() rule in stateful testing. Such a combination had unclear semantics, especially in combination with precondition(), and was never meant to be allowed (issue #2681). 6.5.0 - 2021-03-07 This release adds the explain phase, in which Hypothesis attempts to explain why your test failed by pointing to suspicious lines of code (i.e. those which were always, and only, run on failing inputs). We plan to include “generalising” failing examples in this phase in a future release (issue #2192). 6.4.3 - 2021-03-04 This patch fixes issue #2794, where nesting deferred() strategies within recursive() strategies could trigger an internal assertion. While it was always possible to get the same results from a more sensible strategy, the convoluted form now works too. 6.4.2 - 2021-03-04 This patch fixes several problems with mypy when –no-implicit-reexport was activated in user projects. Thanks to Nikita Sobolev for fixing issue #2884! 6.4.1 - 2021-03-04 This patch fixes an exception that occurs when using type unions of the typing_extensions Literal backport on Python 3.6. Thanks to Ben Anhalt for identifying and fixing this bug. 6.4.0 - 2021-03-02 This release fixes stateful testing methods with multiple precondition() decorators. Previously, only the outer-most precondition was checked (issue #2681). 6.3.4 - 2021-02-28 This patch refactors some internals of RuleBasedStateMachine. There is no change to the public API or behaviour. 6.3.3 - 2021-02-26 This patch moves some internal code, so that future work can avoid creating import cycles. There is no user-visible change. 6.3.2 - 2021-02-25 This patch enables register_type_strategy() for subclasses of typing.TypedDict. Previously, from_type() would ignore the registered strategy (issue #2872). Thanks to Ilya Lebedev for identifying and fixing this bug! 6.3.1 - 2021-02-24 This release lays the groundwork for automatic rewriting of simple filters, for example converting integers().filter(lambda x: x > 9) to integers(min_value=10). Note that this is not supported yet, and we will continue to recommend writing the efficient form directly wherever possible - predicate rewriting is provided mainly for the benefit of downstream libraries which would otherwise have to implement it for themselves (e.g. pandera and icontract-hypothesis). See issue #2701 for details. 6.3.0 - 2021-02-20 The Hypothesis pytest plugin now requires pytest version 4.6 or later. If the plugin detects an earlier version of pytest, it will automatically deactivate itself. (4.6.x is the earliest pytest branch that still accepts community bugfixes.) Hypothesis-based tests should continue to work in earlier versions of pytest, but enhanced integrations provided by the plugin (such as --hypothesis-show-statistics and other command-line flags) will no longer be available in obsolete pytest versions.
2021-03-17 14:13:31 +01:00
${PYSITELIB}/hypothesis/internal/scrutineer.py
${PYSITELIB}/hypothesis/internal/scrutineer.pyc
${PYSITELIB}/hypothesis/internal/scrutineer.pyo
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-16 08:59:55 +01:00
${PYSITELIB}/hypothesis/internal/validation.py
${PYSITELIB}/hypothesis/internal/validation.pyc
${PYSITELIB}/hypothesis/internal/validation.pyo
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-16 20:35:19 +02:00
${PYSITELIB}/hypothesis/provisional.py
${PYSITELIB}/hypothesis/provisional.pyc
${PYSITELIB}/hypothesis/provisional.pyo
py-hypothesis: updated to 3.65.0 3.65.0: This release deprecates the :obj:~hypothesis.settings.max_shrinks setting in favor of an internal heuristic. If you need to avoid shrinking examples, use the :obj:~hypothesis.settings.phases setting instead. (:issue:1235) 3.64.2: This release fixes a bug where an internal assertion error could sometimes be triggered while shrinking a failing test. 3.64.1: This patch fixes type-checking errors in our vendored pretty-printer, which were ignored by our mypy config but visible for anyone else (whoops). Thanks to Pi Delport for reporting :issue:1359 so promptly. 3.64.0: This release adds :ref:an interface <custom-function-execution> which can be used to insert a wrapper between the original test function and :func:@given <hypothesis.given> (:issue:1257). This will be particularly useful for test runner extensions such as :pypi:pytest-trio, but is not recommended for direct use by other users of Hypothesis. 3.63.0: This release adds a new mechanism to infer strategies for classes defined using :pypi:attrs, based on the the type, converter, or validator of each attribute. This inference is now built in to :func:~hypothesis.strategies.builds and :func:~hypothesis.strategies.from_type. On Python 2, :func:~hypothesis.strategies.from_type no longer generates instances of int when passed long, or vice-versa. 3.62.0: This release adds PEP 484 type hints to Hypothesis on a provisional basis, using the comment-based syntax for Python 2 compatibility. You can :ref:read more about our type hints here <our-type-hints>. It also adds the py.typed marker specified in PEP 561. After you pip install hypothesis, :pypi:mypy 0.590 or later will therefore type-check your use of our public interface! 3.61.0: This release deprecates the use of :class:~hypothesis.settings as a context manager, the use of which is somewhat ambiguous. Users should define settings with global state or with the :func:@settings(...) <hypothesis.settings> decorator. 3.60.1: Fixed a bug in generating an instance of a Django model from a strategy where the primary key is generated as part of the strategy. See :ref:details here <django-generating-primary-key>. 3.60.0: This release add initialize decorator for stateful testing (originally discussed in :issue:1216). initialize act as a special rule that is only called once, and all initialize rules are guaranteed to be called before any normal rule is called.
2018-07-03 09:47:45 +02:00
${PYSITELIB}/hypothesis/py.typed
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/reporting.py
${PYSITELIB}/hypothesis/reporting.pyc
${PYSITELIB}/hypothesis/reporting.pyo
${PYSITELIB}/hypothesis/stateful.py
${PYSITELIB}/hypothesis/stateful.pyc
${PYSITELIB}/hypothesis/stateful.pyo
Updated py-hypothesis to 3.5.3. 3.5.3 - 2016-10-05 This is a bug fix release. Bugs fixed: If the same test was running concurrently in two processes and there were examples already in the test database which no longer failed, Hypothesis would sometimes fail with a FileNotFoundError (IOError on Python 2) because an example it was trying to read was deleted before it was read. (Issue #372). Drawing from an integers() strategy with both a min_value and a max_value would reject too many examples needlessly. Now it repeatedly redraws until satisfied. (Pull request #366. Thanks to Calen Pennington for the contribution). 3.5.2 - 2016-09-24 This is a bug fix release. The Hypothesis pytest plugin broke pytest support for doctests. Now it doesn’t. 3.5.1 - 2016-09-23 This is a bug fix release. Hypothesis now runs cleanly in -B and -BB modes, avoiding mixing bytes and unicode. unittest.TestCase tests would now have shown up in the new statistics mode. Now they do. Similarly, stateful tests would not have shown up in statistics and now they do. Statistics now print with pytest node IDs (the names you’d get in pytest verbose mode). 3.5.0 - 2016-09-22 This is a feature release. fractions() and decimals() strategies now support min_value and max_value parameters. Thanks go to Anne Mulhern for the development of this feature. The Hypothesis pytest plugin now supports a –hypothesis-show-statistics parameter that gives detailed statistics about the tests that were run. Huge thanks to Jean-Louis Fuchs and Adfinis-SyGroup for funding the development of this feature. There is a new event() function that can be used to add custom statistics. Additionally there have been some minor bug fixes: In some cases Hypothesis should produce fewer duplicate examples (this will mostly only affect cases with a single parameter). py.test command line parameters are now under an option group for Hypothesis (thanks to David Keijser for fixing this) Hypothesis would previously error if you used function annotations on your tests under Python 3.4. The repr of many strategies using lambdas has been improved to include the lambda body (this was previously supported in many but not all cases).
2016-10-19 14:42:56 +02:00
${PYSITELIB}/hypothesis/statistics.py
${PYSITELIB}/hypothesis/statistics.pyc
${PYSITELIB}/hypothesis/statistics.pyo
py-hypothesis: updated to 4.53.3 4.53.3: This patch fixes :func:`~hypothesis.strategies.from_type` with :class:`python:typing.Hashable` and :class:`python:typing.Sized`, which previously failed with an internal error on Python 3.7 or later. 4.53.2: This release reorganises a number of the Hypothesis internal modules into a package structure. If you are only depending on the public API it should have no effect. If you are depending on the internal API (which you shouldn't be, and which we don't guarantee compatibility on) you may have to rename some imports. 4.53.1: This release changes the size distribution of the number of steps run in stateful testing: It will now almost always run the maximum number of steps permitted. 4.53.0: :ref:`statistics` now include the best score seen for each label, which can help avoid the threshold problem when the minimal example shrinks right down to the threshold of failure (:issue:`2180`). 4.52.0: This release changes the stateful_step_count setting to raise an error if set to 0. This is a backwards compatible change because a value of 0 would never have worked and attempting to run it would have resulted in an internal assertion error. 4.51.1: This release makes a small internal change to the distribution of test cases. It is unlikely to have much user visible impact. 4.51.0: This release deprecates use of :func:`@example <hypothesis.example>`, :func:`@seed <hypothesis.seed>`, or :func:`@reproduce_failure <hypothesis.reproduce_failure>` without :func:`@given <hypothesis.given>`. 4.50.8: This patch makes certain uses of Bundles more efficient in stateful testing (:issue:`2078`). 4.50.7: This release refactors some of Hypothesis's internal interfaces for representing data generation. It should have no user visible effect. 4.50.6: This patch removes some old debugging helpers in our Numpy extra which have not been needed since :issue:`1963` and :issue:`2245`. 4.50.5: This patch fixes :issue:`2229`, where Numpy arrays of unsized strings would only ever have strings of size one due to an interaction between our generation logic and Numpy's allocation strategy. 4.50.4: This patch fixes a rare internal error in strategies for a list of unique items sampled from a short non-unique sequence (:issue:`2247`). The bug was discovered via :pypi:`hypothesis-jsonschema`. 4.50.3: This release improves the error message when :func:`@settings <hypothesis.settings>` tries to inherit settings from a parent argument that isn't a settings instance. 4.50.2: This release improves Hypothesis's "Falsifying example" output, by breaking output across multiple lines where necessary, and by removing irrelevant information from the stateful testing output. 4.50.1: This patch adds :pypi:`flake8-comprehensions` to our linter suite. There is no user-visible change - expect perhaps via some strange microbenchmarks - but certain parts of the code now have a clear and more consistent style. 4.50.0: This release fixes some cases where we might previously have failed to run the validation logic for some strategies. As a result tests which would previously have been silently testing significantly less than they should may now start to raise InvalidArgument now that these errors are caught. 4.49.0: This release significantly improves the data distribution in :doc:`rule based stateful testing <stateful>`, by using a technique called Swarm Testing (Groce, Alex, et al. "Swarm testing." Proceedings of the 2012 International Symposium on Software Testing and Analysis. ACM, 2012.) to select which rules are run in any given test case. This should allow it to find many issues that it would previously have missed. This change is likely to be especially beneficial for stateful tests with large numbers of rules. 4.48.1: This release adds some heuristics to test case generation that try to ensure that test cases generated early on will be relatively small. This fixes a bug introduced in :ref:`Hypothesis 4.42.0 <v4.42.0>` which would cause occasional :obj:`~hypothesis.HealthCheck.too_slow` failures on some tests. 4.48.0: This release revokes the deprecation of find, as we've now rebuilt it on top of @given, which means it has minimal maintenance burden and we're happy to support it. 4.47.5: This release rebuilds find() on top of @given in order to have more code in common. It should have minimal user visible effect. 4.47.4: This patch removes an internal compatibility shim that we no longer need. 4.47.3: This patch fixes several typos in our docstrings and comments, with no change in behaviour. 4.47.2: This release fixes an internal issue where Hypothesis would sometimes generate test cases that were above its intended maximum size. This would only have happened rarely and probably would not have caused major problems when it did. Users of the new :ref:`targeted property-based testing <targeted-search>` might see minor impact (possibly slightly faster tests and slightly worse target scores), but only in the unlikely event that they were hitting this problem. Other users should not see any effect at all. 4.47.1: This release removes some unused code from the core engine. There is no user-visible change. 4.47.0: This release commonizes some code between running explicit examples and normal test execution. The main user visible impact of this is that deadlines are now enforced when running explicit examples. 4.46.1: This patch ensures that a KeyboardInterrupt received during example generation is not treated as a mystery test failure but instead propagates to the top level, not recording the interrupted generation in the conjecture data tree. 4.46.0: This release changes the behaviour of :func:`~hypothesis.strategies.floats` when excluding signed zeros - floats(max_value=0.0, exclude_max=True) can no longer generate -0.0 nor the much rarer floats(min_value=-0.0, exclude_min=True) generate +0.0. The correct interaction between signed zeros and exclusive endpoints was unclear; we now enforce the invariant that :func:`~hypothesis.strategies.floats` will never generate a value equal to an excluded endpoint (:issue:`2201`). If you prefer the old behaviour, you can pass floats(max_value=-0.0) or floats(min_value=0.0) which is exactly equivalent and has not changed. If you had two endpoints equal to zero, we recommend clarifying your tests by using :func:`~hypothesis.strategies.just` or :func:`~hypothesis.strategies.sampled_from` instead of :func:`~hypothesis.strategies.floats`. 4.45.1: This patch improves the error message when invalid arguments are passed to :func:`~hypothesis.stateful.rule` or :func:`~hypothesis.stateful.invariant` (:issue:`2149`). 4.45.0: This release supports :obj:`python:typing.Final` and :obj:`python:typing.TypedDict` in :func:`~hypothesis.strategies.from_type`. 4.44.5: This patch disables our :pypi:`pytest` plugin when running on versions of :pypi:`pytest` before 4.3, the oldest our plugin supports. Note that at time of writing the Pytest developers only support 4.6 and later! Hypothesis tests using :func:`@given() <hypothesis.given>` work on any test runner, but our integrations to e.g. avoid example database collisions when combined with @pytest.mark.parametrize eventually drop support for obsolete versions. 4.44.4: This patch adds some internal comments and clarifications to the Hypothesis implementation. There is no user-visible change. 4.44.3: This patch avoids importing test runners such as :pypi:`pytest`, :pypi:`unittest2`, or :pypi:`nose` solely to access their special "skip test" exception types - if the module is not in :obj:`sys.modules`, the exception can't be raised anyway. This fixes a problem where importing an otherwise unused module could cause spurious errors due to import-time side effects (and possibly -Werror).
2019-12-15 12:28:53 +01:00
${PYSITELIB}/hypothesis/strategies/__init__.py
${PYSITELIB}/hypothesis/strategies/__init__.pyc
${PYSITELIB}/hypothesis/strategies/__init__.pyo
${PYSITELIB}/hypothesis/strategies/_internal/__init__.py
${PYSITELIB}/hypothesis/strategies/_internal/__init__.pyc
${PYSITELIB}/hypothesis/strategies/_internal/__init__.pyo
${PYSITELIB}/hypothesis/strategies/_internal/attrs.py
${PYSITELIB}/hypothesis/strategies/_internal/attrs.pyc
${PYSITELIB}/hypothesis/strategies/_internal/attrs.pyo
${PYSITELIB}/hypothesis/strategies/_internal/collections.py
${PYSITELIB}/hypothesis/strategies/_internal/collections.pyc
${PYSITELIB}/hypothesis/strategies/_internal/collections.pyo
${PYSITELIB}/hypothesis/strategies/_internal/core.py
${PYSITELIB}/hypothesis/strategies/_internal/core.pyc
${PYSITELIB}/hypothesis/strategies/_internal/core.pyo
${PYSITELIB}/hypothesis/strategies/_internal/datetime.py
${PYSITELIB}/hypothesis/strategies/_internal/datetime.pyc
${PYSITELIB}/hypothesis/strategies/_internal/datetime.pyo
${PYSITELIB}/hypothesis/strategies/_internal/deferred.py
${PYSITELIB}/hypothesis/strategies/_internal/deferred.pyc
${PYSITELIB}/hypothesis/strategies/_internal/deferred.pyo
${PYSITELIB}/hypothesis/strategies/_internal/featureflags.py
${PYSITELIB}/hypothesis/strategies/_internal/featureflags.pyc
${PYSITELIB}/hypothesis/strategies/_internal/featureflags.pyo
${PYSITELIB}/hypothesis/strategies/_internal/flatmapped.py
${PYSITELIB}/hypothesis/strategies/_internal/flatmapped.pyc
${PYSITELIB}/hypothesis/strategies/_internal/flatmapped.pyo
${PYSITELIB}/hypothesis/strategies/_internal/functions.py
${PYSITELIB}/hypothesis/strategies/_internal/functions.pyc
${PYSITELIB}/hypothesis/strategies/_internal/functions.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/strategies/_internal/ipaddress.py
${PYSITELIB}/hypothesis/strategies/_internal/ipaddress.pyc
${PYSITELIB}/hypothesis/strategies/_internal/ipaddress.pyo
py-hypothesis: updated to 4.53.3 4.53.3: This patch fixes :func:`~hypothesis.strategies.from_type` with :class:`python:typing.Hashable` and :class:`python:typing.Sized`, which previously failed with an internal error on Python 3.7 or later. 4.53.2: This release reorganises a number of the Hypothesis internal modules into a package structure. If you are only depending on the public API it should have no effect. If you are depending on the internal API (which you shouldn't be, and which we don't guarantee compatibility on) you may have to rename some imports. 4.53.1: This release changes the size distribution of the number of steps run in stateful testing: It will now almost always run the maximum number of steps permitted. 4.53.0: :ref:`statistics` now include the best score seen for each label, which can help avoid the threshold problem when the minimal example shrinks right down to the threshold of failure (:issue:`2180`). 4.52.0: This release changes the stateful_step_count setting to raise an error if set to 0. This is a backwards compatible change because a value of 0 would never have worked and attempting to run it would have resulted in an internal assertion error. 4.51.1: This release makes a small internal change to the distribution of test cases. It is unlikely to have much user visible impact. 4.51.0: This release deprecates use of :func:`@example <hypothesis.example>`, :func:`@seed <hypothesis.seed>`, or :func:`@reproduce_failure <hypothesis.reproduce_failure>` without :func:`@given <hypothesis.given>`. 4.50.8: This patch makes certain uses of Bundles more efficient in stateful testing (:issue:`2078`). 4.50.7: This release refactors some of Hypothesis's internal interfaces for representing data generation. It should have no user visible effect. 4.50.6: This patch removes some old debugging helpers in our Numpy extra which have not been needed since :issue:`1963` and :issue:`2245`. 4.50.5: This patch fixes :issue:`2229`, where Numpy arrays of unsized strings would only ever have strings of size one due to an interaction between our generation logic and Numpy's allocation strategy. 4.50.4: This patch fixes a rare internal error in strategies for a list of unique items sampled from a short non-unique sequence (:issue:`2247`). The bug was discovered via :pypi:`hypothesis-jsonschema`. 4.50.3: This release improves the error message when :func:`@settings <hypothesis.settings>` tries to inherit settings from a parent argument that isn't a settings instance. 4.50.2: This release improves Hypothesis's "Falsifying example" output, by breaking output across multiple lines where necessary, and by removing irrelevant information from the stateful testing output. 4.50.1: This patch adds :pypi:`flake8-comprehensions` to our linter suite. There is no user-visible change - expect perhaps via some strange microbenchmarks - but certain parts of the code now have a clear and more consistent style. 4.50.0: This release fixes some cases where we might previously have failed to run the validation logic for some strategies. As a result tests which would previously have been silently testing significantly less than they should may now start to raise InvalidArgument now that these errors are caught. 4.49.0: This release significantly improves the data distribution in :doc:`rule based stateful testing <stateful>`, by using a technique called Swarm Testing (Groce, Alex, et al. "Swarm testing." Proceedings of the 2012 International Symposium on Software Testing and Analysis. ACM, 2012.) to select which rules are run in any given test case. This should allow it to find many issues that it would previously have missed. This change is likely to be especially beneficial for stateful tests with large numbers of rules. 4.48.1: This release adds some heuristics to test case generation that try to ensure that test cases generated early on will be relatively small. This fixes a bug introduced in :ref:`Hypothesis 4.42.0 <v4.42.0>` which would cause occasional :obj:`~hypothesis.HealthCheck.too_slow` failures on some tests. 4.48.0: This release revokes the deprecation of find, as we've now rebuilt it on top of @given, which means it has minimal maintenance burden and we're happy to support it. 4.47.5: This release rebuilds find() on top of @given in order to have more code in common. It should have minimal user visible effect. 4.47.4: This patch removes an internal compatibility shim that we no longer need. 4.47.3: This patch fixes several typos in our docstrings and comments, with no change in behaviour. 4.47.2: This release fixes an internal issue where Hypothesis would sometimes generate test cases that were above its intended maximum size. This would only have happened rarely and probably would not have caused major problems when it did. Users of the new :ref:`targeted property-based testing <targeted-search>` might see minor impact (possibly slightly faster tests and slightly worse target scores), but only in the unlikely event that they were hitting this problem. Other users should not see any effect at all. 4.47.1: This release removes some unused code from the core engine. There is no user-visible change. 4.47.0: This release commonizes some code between running explicit examples and normal test execution. The main user visible impact of this is that deadlines are now enforced when running explicit examples. 4.46.1: This patch ensures that a KeyboardInterrupt received during example generation is not treated as a mystery test failure but instead propagates to the top level, not recording the interrupted generation in the conjecture data tree. 4.46.0: This release changes the behaviour of :func:`~hypothesis.strategies.floats` when excluding signed zeros - floats(max_value=0.0, exclude_max=True) can no longer generate -0.0 nor the much rarer floats(min_value=-0.0, exclude_min=True) generate +0.0. The correct interaction between signed zeros and exclusive endpoints was unclear; we now enforce the invariant that :func:`~hypothesis.strategies.floats` will never generate a value equal to an excluded endpoint (:issue:`2201`). If you prefer the old behaviour, you can pass floats(max_value=-0.0) or floats(min_value=0.0) which is exactly equivalent and has not changed. If you had two endpoints equal to zero, we recommend clarifying your tests by using :func:`~hypothesis.strategies.just` or :func:`~hypothesis.strategies.sampled_from` instead of :func:`~hypothesis.strategies.floats`. 4.45.1: This patch improves the error message when invalid arguments are passed to :func:`~hypothesis.stateful.rule` or :func:`~hypothesis.stateful.invariant` (:issue:`2149`). 4.45.0: This release supports :obj:`python:typing.Final` and :obj:`python:typing.TypedDict` in :func:`~hypothesis.strategies.from_type`. 4.44.5: This patch disables our :pypi:`pytest` plugin when running on versions of :pypi:`pytest` before 4.3, the oldest our plugin supports. Note that at time of writing the Pytest developers only support 4.6 and later! Hypothesis tests using :func:`@given() <hypothesis.given>` work on any test runner, but our integrations to e.g. avoid example database collisions when combined with @pytest.mark.parametrize eventually drop support for obsolete versions. 4.44.4: This patch adds some internal comments and clarifications to the Hypothesis implementation. There is no user-visible change. 4.44.3: This patch avoids importing test runners such as :pypi:`pytest`, :pypi:`unittest2`, or :pypi:`nose` solely to access their special "skip test" exception types - if the module is not in :obj:`sys.modules`, the exception can't be raised anyway. This fixes a problem where importing an otherwise unused module could cause spurious errors due to import-time side effects (and possibly -Werror).
2019-12-15 12:28:53 +01:00
${PYSITELIB}/hypothesis/strategies/_internal/lazy.py
${PYSITELIB}/hypothesis/strategies/_internal/lazy.pyc
${PYSITELIB}/hypothesis/strategies/_internal/lazy.pyo
${PYSITELIB}/hypothesis/strategies/_internal/misc.py
${PYSITELIB}/hypothesis/strategies/_internal/misc.pyc
${PYSITELIB}/hypothesis/strategies/_internal/misc.pyo
${PYSITELIB}/hypothesis/strategies/_internal/numbers.py
${PYSITELIB}/hypothesis/strategies/_internal/numbers.pyc
${PYSITELIB}/hypothesis/strategies/_internal/numbers.pyo
py-hypothesis: update to 5.37.0. About a year of changes that are only available on a very detailed level. Biggest change: stop supporting Python 2.x Detailed changes here: https://hypothesis.readthedocs.io/en/latest/changes.html
2020-10-06 12:52:29 +02:00
${PYSITELIB}/hypothesis/strategies/_internal/random.py
${PYSITELIB}/hypothesis/strategies/_internal/random.pyc
${PYSITELIB}/hypothesis/strategies/_internal/random.pyo
py-hypothesis: updated to 4.53.3 4.53.3: This patch fixes :func:`~hypothesis.strategies.from_type` with :class:`python:typing.Hashable` and :class:`python:typing.Sized`, which previously failed with an internal error on Python 3.7 or later. 4.53.2: This release reorganises a number of the Hypothesis internal modules into a package structure. If you are only depending on the public API it should have no effect. If you are depending on the internal API (which you shouldn't be, and which we don't guarantee compatibility on) you may have to rename some imports. 4.53.1: This release changes the size distribution of the number of steps run in stateful testing: It will now almost always run the maximum number of steps permitted. 4.53.0: :ref:`statistics` now include the best score seen for each label, which can help avoid the threshold problem when the minimal example shrinks right down to the threshold of failure (:issue:`2180`). 4.52.0: This release changes the stateful_step_count setting to raise an error if set to 0. This is a backwards compatible change because a value of 0 would never have worked and attempting to run it would have resulted in an internal assertion error. 4.51.1: This release makes a small internal change to the distribution of test cases. It is unlikely to have much user visible impact. 4.51.0: This release deprecates use of :func:`@example <hypothesis.example>`, :func:`@seed <hypothesis.seed>`, or :func:`@reproduce_failure <hypothesis.reproduce_failure>` without :func:`@given <hypothesis.given>`. 4.50.8: This patch makes certain uses of Bundles more efficient in stateful testing (:issue:`2078`). 4.50.7: This release refactors some of Hypothesis's internal interfaces for representing data generation. It should have no user visible effect. 4.50.6: This patch removes some old debugging helpers in our Numpy extra which have not been needed since :issue:`1963` and :issue:`2245`. 4.50.5: This patch fixes :issue:`2229`, where Numpy arrays of unsized strings would only ever have strings of size one due to an interaction between our generation logic and Numpy's allocation strategy. 4.50.4: This patch fixes a rare internal error in strategies for a list of unique items sampled from a short non-unique sequence (:issue:`2247`). The bug was discovered via :pypi:`hypothesis-jsonschema`. 4.50.3: This release improves the error message when :func:`@settings <hypothesis.settings>` tries to inherit settings from a parent argument that isn't a settings instance. 4.50.2: This release improves Hypothesis's "Falsifying example" output, by breaking output across multiple lines where necessary, and by removing irrelevant information from the stateful testing output. 4.50.1: This patch adds :pypi:`flake8-comprehensions` to our linter suite. There is no user-visible change - expect perhaps via some strange microbenchmarks - but certain parts of the code now have a clear and more consistent style. 4.50.0: This release fixes some cases where we might previously have failed to run the validation logic for some strategies. As a result tests which would previously have been silently testing significantly less than they should may now start to raise InvalidArgument now that these errors are caught. 4.49.0: This release significantly improves the data distribution in :doc:`rule based stateful testing <stateful>`, by using a technique called Swarm Testing (Groce, Alex, et al. "Swarm testing." Proceedings of the 2012 International Symposium on Software Testing and Analysis. ACM, 2012.) to select which rules are run in any given test case. This should allow it to find many issues that it would previously have missed. This change is likely to be especially beneficial for stateful tests with large numbers of rules. 4.48.1: This release adds some heuristics to test case generation that try to ensure that test cases generated early on will be relatively small. This fixes a bug introduced in :ref:`Hypothesis 4.42.0 <v4.42.0>` which would cause occasional :obj:`~hypothesis.HealthCheck.too_slow` failures on some tests. 4.48.0: This release revokes the deprecation of find, as we've now rebuilt it on top of @given, which means it has minimal maintenance burden and we're happy to support it. 4.47.5: This release rebuilds find() on top of @given in order to have more code in common. It should have minimal user visible effect. 4.47.4: This patch removes an internal compatibility shim that we no longer need. 4.47.3: This patch fixes several typos in our docstrings and comments, with no change in behaviour. 4.47.2: This release fixes an internal issue where Hypothesis would sometimes generate test cases that were above its intended maximum size. This would only have happened rarely and probably would not have caused major problems when it did. Users of the new :ref:`targeted property-based testing <targeted-search>` might see minor impact (possibly slightly faster tests and slightly worse target scores), but only in the unlikely event that they were hitting this problem. Other users should not see any effect at all. 4.47.1: This release removes some unused code from the core engine. There is no user-visible change. 4.47.0: This release commonizes some code between running explicit examples and normal test execution. The main user visible impact of this is that deadlines are now enforced when running explicit examples. 4.46.1: This patch ensures that a KeyboardInterrupt received during example generation is not treated as a mystery test failure but instead propagates to the top level, not recording the interrupted generation in the conjecture data tree. 4.46.0: This release changes the behaviour of :func:`~hypothesis.strategies.floats` when excluding signed zeros - floats(max_value=0.0, exclude_max=True) can no longer generate -0.0 nor the much rarer floats(min_value=-0.0, exclude_min=True) generate +0.0. The correct interaction between signed zeros and exclusive endpoints was unclear; we now enforce the invariant that :func:`~hypothesis.strategies.floats` will never generate a value equal to an excluded endpoint (:issue:`2201`). If you prefer the old behaviour, you can pass floats(max_value=-0.0) or floats(min_value=0.0) which is exactly equivalent and has not changed. If you had two endpoints equal to zero, we recommend clarifying your tests by using :func:`~hypothesis.strategies.just` or :func:`~hypothesis.strategies.sampled_from` instead of :func:`~hypothesis.strategies.floats`. 4.45.1: This patch improves the error message when invalid arguments are passed to :func:`~hypothesis.stateful.rule` or :func:`~hypothesis.stateful.invariant` (:issue:`2149`). 4.45.0: This release supports :obj:`python:typing.Final` and :obj:`python:typing.TypedDict` in :func:`~hypothesis.strategies.from_type`. 4.44.5: This patch disables our :pypi:`pytest` plugin when running on versions of :pypi:`pytest` before 4.3, the oldest our plugin supports. Note that at time of writing the Pytest developers only support 4.6 and later! Hypothesis tests using :func:`@given() <hypothesis.given>` work on any test runner, but our integrations to e.g. avoid example database collisions when combined with @pytest.mark.parametrize eventually drop support for obsolete versions. 4.44.4: This patch adds some internal comments and clarifications to the Hypothesis implementation. There is no user-visible change. 4.44.3: This patch avoids importing test runners such as :pypi:`pytest`, :pypi:`unittest2`, or :pypi:`nose` solely to access their special "skip test" exception types - if the module is not in :obj:`sys.modules`, the exception can't be raised anyway. This fixes a problem where importing an otherwise unused module could cause spurious errors due to import-time side effects (and possibly -Werror).
2019-12-15 12:28:53 +01:00
${PYSITELIB}/hypothesis/strategies/_internal/recursive.py
${PYSITELIB}/hypothesis/strategies/_internal/recursive.pyc
${PYSITELIB}/hypothesis/strategies/_internal/recursive.pyo
${PYSITELIB}/hypothesis/strategies/_internal/regex.py
${PYSITELIB}/hypothesis/strategies/_internal/regex.pyc
${PYSITELIB}/hypothesis/strategies/_internal/regex.pyo
${PYSITELIB}/hypothesis/strategies/_internal/shared.py
${PYSITELIB}/hypothesis/strategies/_internal/shared.pyc
${PYSITELIB}/hypothesis/strategies/_internal/shared.pyo
${PYSITELIB}/hypothesis/strategies/_internal/strategies.py
${PYSITELIB}/hypothesis/strategies/_internal/strategies.pyc
${PYSITELIB}/hypothesis/strategies/_internal/strategies.pyo
${PYSITELIB}/hypothesis/strategies/_internal/strings.py
${PYSITELIB}/hypothesis/strategies/_internal/strings.pyc
${PYSITELIB}/hypothesis/strategies/_internal/strings.pyo
${PYSITELIB}/hypothesis/strategies/_internal/types.py
${PYSITELIB}/hypothesis/strategies/_internal/types.pyc
${PYSITELIB}/hypothesis/strategies/_internal/types.pyo
py-hypothesis: update to 6.8.1. 6.8.1 - 2021-03-14 This patch lays more groundwork for filter rewriting (issue #2701). There is no user-visible change… yet. 6.8.0 - 2021-03-11 This release registers the remaining builtin types, and teaches from_type() to try resolving ForwardRef and Type references to built-in types. 6.7.0 - 2021-03-10 This release teaches RuleBasedStateMachine to avoid checking invariant()s until all initialize() rules have been run. You can enable checking of specific invariants for incompletely initialized machines by using @invariant(check_during_init=True) (issue #2868). In previous versions, it was possible if awkward to implement this behaviour using precondition() and an auxiliary variable. 6.6.1 - 2021-03-09 This patch improves the error message when from_type() fails to resolve a forward-reference inside a typing.Type such as Type["int"] (issue #2565). 6.6.0 - 2021-03-07 This release makes it an explicit error to apply invariant() to a rule() or initialize() rule in stateful testing. Such a combination had unclear semantics, especially in combination with precondition(), and was never meant to be allowed (issue #2681). 6.5.0 - 2021-03-07 This release adds the explain phase, in which Hypothesis attempts to explain why your test failed by pointing to suspicious lines of code (i.e. those which were always, and only, run on failing inputs). We plan to include “generalising” failing examples in this phase in a future release (issue #2192). 6.4.3 - 2021-03-04 This patch fixes issue #2794, where nesting deferred() strategies within recursive() strategies could trigger an internal assertion. While it was always possible to get the same results from a more sensible strategy, the convoluted form now works too. 6.4.2 - 2021-03-04 This patch fixes several problems with mypy when –no-implicit-reexport was activated in user projects. Thanks to Nikita Sobolev for fixing issue #2884! 6.4.1 - 2021-03-04 This patch fixes an exception that occurs when using type unions of the typing_extensions Literal backport on Python 3.6. Thanks to Ben Anhalt for identifying and fixing this bug. 6.4.0 - 2021-03-02 This release fixes stateful testing methods with multiple precondition() decorators. Previously, only the outer-most precondition was checked (issue #2681). 6.3.4 - 2021-02-28 This patch refactors some internals of RuleBasedStateMachine. There is no change to the public API or behaviour. 6.3.3 - 2021-02-26 This patch moves some internal code, so that future work can avoid creating import cycles. There is no user-visible change. 6.3.2 - 2021-02-25 This patch enables register_type_strategy() for subclasses of typing.TypedDict. Previously, from_type() would ignore the registered strategy (issue #2872). Thanks to Ilya Lebedev for identifying and fixing this bug! 6.3.1 - 2021-02-24 This release lays the groundwork for automatic rewriting of simple filters, for example converting integers().filter(lambda x: x > 9) to integers(min_value=10). Note that this is not supported yet, and we will continue to recommend writing the efficient form directly wherever possible - predicate rewriting is provided mainly for the benefit of downstream libraries which would otherwise have to implement it for themselves (e.g. pandera and icontract-hypothesis). See issue #2701 for details. 6.3.0 - 2021-02-20 The Hypothesis pytest plugin now requires pytest version 4.6 or later. If the plugin detects an earlier version of pytest, it will automatically deactivate itself. (4.6.x is the earliest pytest branch that still accepts community bugfixes.) Hypothesis-based tests should continue to work in earlier versions of pytest, but enhanced integrations provided by the plugin (such as --hypothesis-show-statistics and other command-line flags) will no longer be available in obsolete pytest versions.
2021-03-17 14:13:31 +01:00
${PYSITELIB}/hypothesis/strategies/_internal/utils.py
${PYSITELIB}/hypothesis/strategies/_internal/utils.pyc
${PYSITELIB}/hypothesis/strategies/_internal/utils.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/utils/__init__.py
${PYSITELIB}/hypothesis/utils/__init__.pyc
${PYSITELIB}/hypothesis/utils/__init__.pyo
${PYSITELIB}/hypothesis/utils/conventions.py
${PYSITELIB}/hypothesis/utils/conventions.pyc
${PYSITELIB}/hypothesis/utils/conventions.pyo
${PYSITELIB}/hypothesis/utils/dynamicvariables.py
${PYSITELIB}/hypothesis/utils/dynamicvariables.pyc
${PYSITELIB}/hypothesis/utils/dynamicvariables.pyo
py-hypothesis: updated to 6.27.1 6.27.1 This patch changes the backing datastructures of register_random() and a few internal caches to use weakref.WeakKeyDictionary. This reduces memory usage and may improve performance when registered Random instances are only used for a subset of your tests. 6.27.0 This release teaches Hypothesis’ multiple-error reporting to format tracebacks using pytest or better-exceptions, if they are installed and enabled. 6.26.0 Did you know that of the 264 possible floating-point numbers, 253 of them are nan While nans usually have all zeros in the sign bit and mantissa, this isn’t always true, and ‘signaling’ nans might trap or error. To help distinguish such errors in e.g. CI logs, Hypothesis now prints -nan for negative nans, and adds a comment like # Saw 3 signaling NaNs if applicable. 6.25.0 This release adds special filtering logic to make a few special cases like s.map(lambda x: x) and lists().filter(len) more efficient. 6.24.6 This patch makes floats() generate “subnormal” floating point numbers more often, as these rare values can have strange interactions with unsafe compiler optimisations like -ffast-math. 6.24.5 This patch fixes a rare internal error in the datetimes() strategy, where the implementation of allow_imaginary=False crashed when checking a time during the skipped hour of a DST transition if the DST offset is negative 6.24.4 This patch gives Hypothesis it’s own internal Random instance, ensuring that test suites which reset the global random state don’t induce weird correlations between property-based tests. 6.24.3 This patch updates documentation of note()
2021-11-25 21:01:56 +01:00
${PYSITELIB}/hypothesis/utils/terminal.py
${PYSITELIB}/hypothesis/utils/terminal.pyc
${PYSITELIB}/hypothesis/utils/terminal.pyo
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/vendor/__init__.py
${PYSITELIB}/hypothesis/vendor/__init__.pyc
${PYSITELIB}/hypothesis/vendor/__init__.pyo
${PYSITELIB}/hypothesis/vendor/pretty.py
${PYSITELIB}/hypothesis/vendor/pretty.pyc
${PYSITELIB}/hypothesis/vendor/pretty.pyo
py-hypothesis: updated to 4.33.1 4.33.1: This patch works around a crash when an incompatible version of Numpy is installed under PyPy 5.10 (Python 2.7). If you are still using Python 2, please upgrade to Python 3 as soon as possible - it will be unsupported at the end of this year. 4.33.0: This release improves the :func:~hypothesis.provisional.domains strategy, as well as the :func:~hypothesis.provisional.urls and the :func:~hypothesis.strategies.emails strategies which use it. These strategies now use the full IANA list of Top Level Domains and are correct as per :rfc:1035. Passing tests using these strategies may now fail. 4.32.3: This patch tidies up the repr of several settings-related objects, at runtime and in the documentation, and deprecates the undocumented edge case that phases=None was treated like phases=tuple(Phase). It *also* fixes :func:~hypothesis.extra.lark.from_lark with :pypi:lark 0.7.2 <lark-parser> and later. 4.32.2: This patch updates some internal comments for :pypi:mypy 0.720. There is no user-visible impact. 4.32.1: This release changes how the shrinker represents its progress internally. For large generated test cases this should result in significantly less memory usage and possibly faster shrinking. Small generated test cases may be slightly slower to shrink but this shouldn't be very noticeable. 4.32.0: This release makes :func:~hypothesis.extra.numpy.arrays more pedantic about elements strategies that cannot be exactly represented as array elements. In practice, you will see new warnings if you were using a float16 or float32 dtype without passing :func:~hypothesis.strategies.floats the width=16 or width=32 arguments respectively. The previous behaviour could lead to silent truncation, and thus some elements being equal to an explicitly excluded bound (:issue:1899). 4.31.1: This patch changes an internal use of MD5 to SHA hashes, to better support users subject to FIPS-140. There is no user-visible or API change. 4.31.0: This release simplifies the logic of the :attr:~hypothesis.settings.print_blob setting by removing the option to set it to PrintSettings.INFER. As a result the print_blob setting now takes a single boolean value, and the use of PrintSettings is deprecated. 4.28.2: This patch improves the docstrings of several Hypothesis strategies, by clarifying markup and adding cross-references. There is no runtime change. 4.28.1: This patch improves the behaviour of the :func:~hypothesis.strategies.text strategy when passed an alphabet which is not a strategy. The value is now interpreted as whitelist_characters to :func:~hypothesis.strategies.characters instead of a sequence for :func:~hypothesis.strategies.sampled_from, which standardises the distribution of examples and the shrinking behaviour. You can get the previous behaviour by using lists(sampled_from(alphabet)).map("".map) instead. 4.28.0: This release deprecates find(). The .example() method is a better replacement if you want *an* example, and for the rare occasions where you want the *minimal* example you can get it from :func:@given <hypothesis.given>. :func:@given <hypothesis.given> has steadily outstripped find() in both features and performance over recent years, and as we do not have the resources to maintain and test both we think it is better to focus on just one. 4.27.0: This release refactors the implementation of the .example() method, to more accurately represent the data which will be generated by :func:@given <hypothesis.given>. As a result, calling s.example() on an empty strategy s (such as :func:~hypothesis.strategies.nothing) now raises Unsatisfiable instead of the old NoExamples exception. 4.26.4: This patch ensures that the Pandas extra will keep working when Python 3.8 removes abstract base classes from the top-level :obj:python:collections namespace. This also fixes the relevant warning in Python 3.7, but there is no other difference in behaviour and you do not need to do anything. 4.26.3: This release fixes :issue:2027, by changing the way Hypothesis tries to generate distinct examples to be more efficient. This may result in slightly different data distribution, and should improve generation performance in general, but should otherwise have minimal user impact. 4.26.2: This release fixes :issue:1864, where some simple tests would perform very slowly, because they would run many times with each subsequent run being progressively slower. They will now stop after a more reasonable number of runs without hitting this problem. Unless you are hitting exactly this issue, it is unlikely that this release will have any effect, but certain classes of custom generators that are currently very slow may become a bit faster, or start to trigger health check failures. 4.26.1: This release adds the strategy :func:~hypothesis.extra.numpy.integer_array_indices, which generates tuples of Numpy arrays that can be used for advanced indexing <http://www.pythonlikeyoumeanit.com/Module3_IntroducingNumpy/AdvancedIndexing.html#Integer-Array-Indexing>_ to select an array of a specified shape. 4.26.0: This release significantly improves the performance of drawing unique collections whose elements are drawn from :func:~hypothesis.strategies.sampled_from strategies. As a side effect, this detects an error condition that would previously have passed silently: When the min_size argument on a collection with distinct elements is greater than the number of elements being sampled, this will now raise an error. 4.25.1: This release removes some defunct internal functionality that was only being used for testing. It should have no user visible impact. 4.25.0: This release deprecates and disables the buffer_size setting, which should have been treated as a private implementation detail all along. We recommend simply deleting this settings argument. 4.24.6: This patch makes :func:~hypothesis.strategies.datetimes more efficient, as it now handles short months correctly by construction instead of filtering. 4.24.5: This patch improves the development experience by simplifying the tracebacks you will see when e.g. you have used the .map(...) method of a strategy and the mapped function raises an exception. No new exceptions can be raised, nor existing exceptions change anything but their traceback. We're simply using if-statements rather than exceptions for control flow in a certain part of the internals! 4.24.4: This patch fixes :issue:2014, where our compatibility layer broke with version 3.7.4 of the :pypi:typing module backport on PyPI. This issue only affects Python 2. We remind users that Hypothesis, like many other packages, will drop Python 2 support on 2020-01-01 <https://python3statement.org>__ and already has several features that are only available on Python 3. 4.24.3: This patch improves the implementation of an internal wrapper on Python 3.8 beta1 (and will break on the alphas; but they're not meant to be stable). On other versions, there is no change at all.
2019-08-22 13:05:27 +02:00
${PYSITELIB}/hypothesis/vendor/tlds-alpha-by-domain.txt
Import py-hypothesis-3.1.0 as devel/py-hypothesis. 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.
2016-04-24 11:44:35 +02:00
${PYSITELIB}/hypothesis/version.py
${PYSITELIB}/hypothesis/version.pyc
${PYSITELIB}/hypothesis/version.pyo
Reference in a new issue Copy permalink