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

254 lines
12 KiB
Text
Raw Normal View History

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
@comment $NetBSD: PLIST,v 1.28 2019/11/13 21:08:30 adam Exp $
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
${PYSITELIB}/hypothesis/__init__.py
${PYSITELIB}/hypothesis/__init__.pyc
${PYSITELIB}/hypothesis/__init__.pyo
${PYSITELIB}/hypothesis/_settings.py
${PYSITELIB}/hypothesis/_settings.pyc
${PYSITELIB}/hypothesis/_settings.pyo
py-hypothesis: updated to 3.86.5 3.86.5: This is a docs-only patch, which fixes some typos and removes a few hyperlinks for deprecated features. 3.86.4: This release changes the order in which the shrinker tries to delete data. For large and slow tests this may significantly improve the performance of shrinking. 3.86.3: This release fixes a bug where certain places Hypothesis internal errors could be raised during shrinking when a user exception occurred that suppressed an exception Hypothesis uses internally in its generation. The two known ways to trigger this problem were: Errors raised in stateful tests’ teardown function. Errors raised in finally blocks that wrapped a call to data.draw. These cases will now be handled correctly. 3.86.2: This patch is a docs-only change to fix a broken hyperlink. 3.86.1: This patch fixes issue 1732, where integers() would always return long values on Python 2. 3.86.0: This release ensures that infinite numbers are never generated by floats() with allow_infinity=False, which could previously happen in some cases where one bound was also provided. The trivially inconsistent min_value=inf, allow_infinity=False now raises an InvalidArgumentError, as does the inverse with max_value. You can still use just(inf) to generate inf without violating other constraints.
2019-01-07 09:31:28 +01:00
${PYSITELIB}/hypothesis/_strategies.py
${PYSITELIB}/hypothesis/_strategies.pyc
${PYSITELIB}/hypothesis/_strategies.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/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
${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 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
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/models.py
${PYSITELIB}/hypothesis/extra/django/models.pyc
${PYSITELIB}/hypothesis/extra/django/models.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: 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
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
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.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
${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
${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
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: 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/searchstrategy/__init__.py
${PYSITELIB}/hypothesis/searchstrategy/__init__.pyc
${PYSITELIB}/hypothesis/searchstrategy/__init__.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/searchstrategy/attrs.py
${PYSITELIB}/hypothesis/searchstrategy/attrs.pyc
${PYSITELIB}/hypothesis/searchstrategy/attrs.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/searchstrategy/collections.py
${PYSITELIB}/hypothesis/searchstrategy/collections.pyc
${PYSITELIB}/hypothesis/searchstrategy/collections.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/searchstrategy/datetime.py
${PYSITELIB}/hypothesis/searchstrategy/datetime.pyc
${PYSITELIB}/hypothesis/searchstrategy/datetime.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/searchstrategy/deferred.py
${PYSITELIB}/hypothesis/searchstrategy/deferred.pyc
${PYSITELIB}/hypothesis/searchstrategy/deferred.pyo
${PYSITELIB}/hypothesis/searchstrategy/flatmapped.py
${PYSITELIB}/hypothesis/searchstrategy/flatmapped.pyc
${PYSITELIB}/hypothesis/searchstrategy/flatmapped.pyo
py-hypothesis: updated to 4.23.4 4.23.4: Fixes a minor formatting issue the docstring of from_type() 4.23.3: Adds a recipe to the docstring of from_type() that describes a means for drawing values for “everything except” a specified type. This recipe is especially useful for writing tests that perform input-type validation. 4.23.2: This patch uses autoflake to remove some pointless pass statements, which improves our workflow but has no user-visible impact. 4.23.1: This patch fixes an OverflowError in from_type(xrange) on Python 2. It turns out that not only do the start and stop values have to fit in a C long, but so does stop - start. We now handle this even on 32bit platforms, but remind users that Python2 will not be supported after 2019 without specific funding. 4.23.0: This release implements the slices() strategy, to generate slices of a length-size sequence. 4.22.3: This patch exposes DataObject, solely to support more precise type hints. Objects of this type are provided by data(), and can be used to draw examples from strategies intermixed with your test code. 4.22.2: This patch fixes the very rare issue 1798 in array_dtypes(), which caused an internal error in our tests. 4.22.1: This patch fixes a rare bug in from_type(range). 4.22.0: The unique_by argument to lists now accepts a tuple of callables such that every element of the generated list will be unique with respect to each callable in the tuple. 4.21.1: This patch cleans up the internals of one_of(). You may see a slight change to the distribution of examples from this strategy but there is no change to the public API. 4.21.0: The from_type() strategy now supports slice objects. 4.20.0: This release improves the array_shapes() strategy, to choose an appropriate default for max_side based on the min_side, and max_dims based on the min_dims. An explicit error is raised for dimensions greater than 32, which are not supported by Numpy, as for other invalid combinations of arguments. 4.19.0: The from_type() strategy now supports range objects (or xrange on Python 2). 4.18.3: This release fixes a very rare edge case in the test-case mutator, which could cause an internal error with certain unusual tests. 4.18.2: This patch makes Hypothesis compatible with the Python 3.8 alpha, which changed the representation of code objects to support positional-only arguments. Note however that Hypothesis does not (yet) support such functions as e.g. arguments to builds() or inputs to @given. 4.18.1: This patch improves the performance of unique collections such as sets() when the elements are drawn from a sampled_from() strategy. 4.18.0: This release adds the functions() strategy, which can be used to imitate your ‘real’ function for callbacks. 4.17.2: This release refactors stateful rule selection to share the new machinery with sampled_from() instead of using the original independent implementation. 4.17.1: This patch allows Hypothesis to try a few more examples after finding the first bug, in hopes of reporting multiple distinct bugs. The heuristics described in issue 847 ensure that we avoid wasting time on fruitless searches, while still surfacing each bug as soon as possible.
2019-05-09 13:53:58 +02:00
${PYSITELIB}/hypothesis/searchstrategy/functions.py
${PYSITELIB}/hypothesis/searchstrategy/functions.pyc
${PYSITELIB}/hypothesis/searchstrategy/functions.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/searchstrategy/lazy.py
${PYSITELIB}/hypothesis/searchstrategy/lazy.pyc
${PYSITELIB}/hypothesis/searchstrategy/lazy.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/searchstrategy/misc.py
${PYSITELIB}/hypothesis/searchstrategy/misc.pyc
${PYSITELIB}/hypothesis/searchstrategy/misc.pyo
${PYSITELIB}/hypothesis/searchstrategy/numbers.py
${PYSITELIB}/hypothesis/searchstrategy/numbers.pyc
${PYSITELIB}/hypothesis/searchstrategy/numbers.pyo
${PYSITELIB}/hypothesis/searchstrategy/recursive.py
${PYSITELIB}/hypothesis/searchstrategy/recursive.pyc
${PYSITELIB}/hypothesis/searchstrategy/recursive.pyo
3.22.0: This release provides what should be a substantial performance improvement to numpy arrays generated using provided numpy support, and adds a new fill_value argument to arrays() to control this behaviour.
2017-08-27 14:16:06 +02:00
${PYSITELIB}/hypothesis/searchstrategy/regex.py
${PYSITELIB}/hypothesis/searchstrategy/regex.pyc
${PYSITELIB}/hypothesis/searchstrategy/regex.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/searchstrategy/shared.py
${PYSITELIB}/hypothesis/searchstrategy/shared.pyc
${PYSITELIB}/hypothesis/searchstrategy/shared.pyo
${PYSITELIB}/hypothesis/searchstrategy/strategies.py
${PYSITELIB}/hypothesis/searchstrategy/strategies.pyc
${PYSITELIB}/hypothesis/searchstrategy/strategies.pyo
${PYSITELIB}/hypothesis/searchstrategy/strings.py
${PYSITELIB}/hypothesis/searchstrategy/strings.pyc
${PYSITELIB}/hypothesis/searchstrategy/strings.pyo
3.14.0: Hypothesis now understands inline type annotations
2017-07-24 12:23:57 +02:00
${PYSITELIB}/hypothesis/searchstrategy/types.py
${PYSITELIB}/hypothesis/searchstrategy/types.pyc
${PYSITELIB}/hypothesis/searchstrategy/types.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/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
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/strategies.py
${PYSITELIB}/hypothesis/strategies.pyc
${PYSITELIB}/hypothesis/strategies.pyo
${PYSITELIB}/hypothesis/types.py
${PYSITELIB}/hypothesis/types.pyc
${PYSITELIB}/hypothesis/types.pyo
${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
${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