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

186 lines
8.2 KiB
Text
Raw Normal View History

3.12.0: This release makes some major internal changes to how Hypothesis represents data internally, as a prelude to some major engine changes that should improve data quality. There are no API changes, but it's a significant enough internal change that a minor version bump seemed warranted. User facing impact should be fairly mild, but includes: * All existing examples in the database will probably be invalidated. Hypothesis handles this automatically, so you don't need to do anything, but if you see all your examples disappear that's why. * Almost all data distributions have changed significantly. Possibly for the better, possibly for the worse. This may result in new bugs being found, but it may also result in Hypothesis being unable to find bugs it previously did. * Data generation may be somewhat faster if your existing bottleneck was in draw_bytes (which is often the case for large examples). * Shrinking will probably be slower, possibly significantly. If you notice any effects you consider to be a significant regression, please open an issue about them.
2017-07-07 17:41:18 +02:00
@comment $NetBSD: PLIST,v 1.6 2017/07/07 15:41:18 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
${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
${PYSITELIB}/hypothesis/extra/datetime.py
${PYSITELIB}/hypothesis/extra/datetime.pyc
${PYSITELIB}/hypothesis/extra/datetime.pyo
${PYSITELIB}/hypothesis/extra/django/__init__.py
${PYSITELIB}/hypothesis/extra/django/__init__.pyc
${PYSITELIB}/hypothesis/extra/django/__init__.pyo
${PYSITELIB}/hypothesis/extra/django/models.py
${PYSITELIB}/hypothesis/extra/django/models.pyc
${PYSITELIB}/hypothesis/extra/django/models.pyo
${PYSITELIB}/hypothesis/extra/fakefactory.py
${PYSITELIB}/hypothesis/extra/fakefactory.pyc
${PYSITELIB}/hypothesis/extra/fakefactory.pyo
${PYSITELIB}/hypothesis/extra/numpy.py
${PYSITELIB}/hypothesis/extra/numpy.pyc
${PYSITELIB}/hypothesis/extra/numpy.pyo
${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
${PYSITELIB}/hypothesis/internal/charmap.py
${PYSITELIB}/hypothesis/internal/charmap.pyc
${PYSITELIB}/hypothesis/internal/charmap.pyo
${PYSITELIB}/hypothesis/internal/classmap.py
${PYSITELIB}/hypothesis/internal/classmap.pyc
${PYSITELIB}/hypothesis/internal/classmap.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
${PYSITELIB}/hypothesis/internal/conjecture/data.py
${PYSITELIB}/hypothesis/internal/conjecture/data.pyc
${PYSITELIB}/hypothesis/internal/conjecture/data.pyo
${PYSITELIB}/hypothesis/internal/conjecture/engine.py
${PYSITELIB}/hypothesis/internal/conjecture/engine.pyc
${PYSITELIB}/hypothesis/internal/conjecture/engine.pyo
${PYSITELIB}/hypothesis/internal/conjecture/minimizer.py
${PYSITELIB}/hypothesis/internal/conjecture/minimizer.pyc
${PYSITELIB}/hypothesis/internal/conjecture/minimizer.pyo
${PYSITELIB}/hypothesis/internal/conjecture/utils.py
${PYSITELIB}/hypothesis/internal/conjecture/utils.pyc
${PYSITELIB}/hypothesis/internal/conjecture/utils.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/deferredformat.py
${PYSITELIB}/hypothesis/internal/deferredformat.pyc
${PYSITELIB}/hypothesis/internal/deferredformat.pyo
${PYSITELIB}/hypothesis/internal/detection.py
${PYSITELIB}/hypothesis/internal/detection.pyc
${PYSITELIB}/hypothesis/internal/detection.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
${PYSITELIB}/hypothesis/internal/intervalsets.py
${PYSITELIB}/hypothesis/internal/intervalsets.pyc
${PYSITELIB}/hypothesis/internal/intervalsets.pyo
${PYSITELIB}/hypothesis/internal/reflection.py
${PYSITELIB}/hypothesis/internal/reflection.pyc
${PYSITELIB}/hypothesis/internal/reflection.pyo
${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
${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
${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
${PYSITELIB}/hypothesis/searchstrategy/reprwrapper.py
${PYSITELIB}/hypothesis/searchstrategy/reprwrapper.pyc
${PYSITELIB}/hypothesis/searchstrategy/reprwrapper.pyo
${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/streams.py
${PYSITELIB}/hypothesis/searchstrategy/streams.pyc
${PYSITELIB}/hypothesis/searchstrategy/streams.pyo
${PYSITELIB}/hypothesis/searchstrategy/strings.py
${PYSITELIB}/hypothesis/searchstrategy/strings.pyc
${PYSITELIB}/hypothesis/searchstrategy/strings.pyo
${PYSITELIB}/hypothesis/searchstrategy/wrappers.py
${PYSITELIB}/hypothesis/searchstrategy/wrappers.pyc
${PYSITELIB}/hypothesis/searchstrategy/wrappers.pyo
${PYSITELIB}/hypothesis/stateful.py
${PYSITELIB}/hypothesis/stateful.pyc
${PYSITELIB}/hypothesis/stateful.pyo
Updated py-hypothesis to 3.5.3. 3.5.3 - 2016-10-05 This is a bug fix release. Bugs fixed: If the same test was running concurrently in two processes and there were examples already in the test database which no longer failed, Hypothesis would sometimes fail with a FileNotFoundError (IOError on Python 2) because an example it was trying to read was deleted before it was read. (Issue #372). Drawing from an integers() strategy with both a min_value and a max_value would reject too many examples needlessly. Now it repeatedly redraws until satisfied. (Pull request #366. Thanks to Calen Pennington for the contribution). 3.5.2 - 2016-09-24 This is a bug fix release. The Hypothesis pytest plugin broke pytest support for doctests. Now it doesn’t. 3.5.1 - 2016-09-23 This is a bug fix release. Hypothesis now runs cleanly in -B and -BB modes, avoiding mixing bytes and unicode. unittest.TestCase tests would now have shown up in the new statistics mode. Now they do. Similarly, stateful tests would not have shown up in statistics and now they do. Statistics now print with pytest node IDs (the names you’d get in pytest verbose mode). 3.5.0 - 2016-09-22 This is a feature release. fractions() and decimals() strategies now support min_value and max_value parameters. Thanks go to Anne Mulhern for the development of this feature. The Hypothesis pytest plugin now supports a –hypothesis-show-statistics parameter that gives detailed statistics about the tests that were run. Huge thanks to Jean-Louis Fuchs and Adfinis-SyGroup for funding the development of this feature. There is a new event() function that can be used to add custom statistics. Additionally there have been some minor bug fixes: In some cases Hypothesis should produce fewer duplicate examples (this will mostly only affect cases with a single parameter). py.test command line parameters are now under an option group for Hypothesis (thanks to David Keijser for fixing this) Hypothesis would previously error if you used function annotations on your tests under Python 3.4. The repr of many strategies using lambdas has been improved to include the lambda body (this was previously supported in many but not all cases).
2016-10-19 14:42:56 +02:00
${PYSITELIB}/hypothesis/statistics.py
${PYSITELIB}/hypothesis/statistics.pyc
${PYSITELIB}/hypothesis/statistics.pyo
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/strategytests.py
${PYSITELIB}/hypothesis/strategytests.pyc
${PYSITELIB}/hypothesis/strategytests.pyo
${PYSITELIB}/hypothesis/tools/__init__.py
${PYSITELIB}/hypothesis/tools/__init__.pyc
${PYSITELIB}/hypothesis/tools/__init__.pyo
${PYSITELIB}/hypothesis/tools/mergedbs.py
${PYSITELIB}/hypothesis/tools/mergedbs.pyc
${PYSITELIB}/hypothesis/tools/mergedbs.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
${PYSITELIB}/hypothesis/version.py
${PYSITELIB}/hypothesis/version.pyc
${PYSITELIB}/hypothesis/version.pyo
Reference in a new issue Copy permalink