Changelog for python310-hypothesis4-4.57.1-1.90.noarch.rpm :

* Mon Nov 15 2021 Arachnos - update to version 4.57.1:
* This patch improves the type hints and documentation for the django extra. There is no runtime change.- changes from version 4.57.0:
* This release improves support for the SupportsOp protocols from the \"typing\" module when using on \"from_type()\" as outlined in issue [#2292]. The following types now generate much more varied strategies when called with \"from_type()\": + \"typing.SupportsAbs\" + \"typing.SupportsBytes\" + \"typing.SupportsComplex\" + \"typing.SupportsInt\" + \"typing.SupportsFloat\" + \"typing.SupportsRound\"
* Note that using \"from_type()\" with one of the above strategies will not ensure that the the specified function will execute successfully (ie : the strategy returned for \"from_type(typing.SupportsAbs)\" may include NaNs or things this will cause the \"abs()\" function to error. )
* Thanks to Lea Provenzano for this patch.- changes from version 4.56.3:
* This release fixes a small internal bug in shrinking which could have caused it to perform slightly more tests than were necessary. Fixing this shouldn\'t have much effect but it will make shrinking slightly faster.- changes from version 4.56.2:
* This release removes an internal heuristic that was no longer providing much benefit. It is unlikely that there will be any user visible effect.- changes from version 4.56.1:
* This release further improves the optimisation algorithm for targeted property-based testing.- changes from version 4.56.0:
* This release enables deprecation warnings even when the \"verbosity\" setting is \"quiet\", in preparation for Hypothesis 5.0 (issue #2218).
* Warnings can still be filtered by the standard mechanisms provided in the standard-library \"warnings\" module.- changes from version 4.55.4:
* This release improves Hypothesis\'s management of the set of test cases it tracks between runs. It will only do anything if you have \"Phase.target\" enabled and an example database set. In those circumstances it should result in a more thorough and faster set of examples that are tried on each run.- changes from version 4.55.3:
* This release makes Hypothesis better at generating test cases where generated values are duplicated in different parts of the test case. This will be especially noticeable with reasonably complex values, as it was already able to do this for simpler ones such as integers or floats.- changes from version 4.55.2:
* This release expands the set of test cases that Hypothesis saves in its database for future runs to include a representative set of \"structurally different\" test cases - e.g. it might try to save test cases where a given list is empty or not.
* Currently this is unlikely to have much user visible impact except to produce slightly more consistent behaviour between consecutive runs of a test suite. It is mostly groundwork for future improvements which will exploit this functionality more effectively.- changes from version 4.55.1:
* This patch fixes issue #2257, where \"from_type()\" could incorrectly generate bytestrings when passed a generic \"typing.Sequence\" such as \"Sequence[set]\".- changes from version 4.55.0:
* This release adds database support for targeted property-based testing, so the best examples based on the targeting will be saved and reused between runs. This is mostly laying groundwork for future features in this area, but will also make targeted property-based tests more useful during development, where the same tests tend to get run over and over again.
* If \"max_examples\" is large, this may increase memory usage significantly under some circumstances, but these should be relatively rare.
* This release also adds a dependency on the sortedcontainers package.- changes from version 4.54.2:
* This release improves the optimisation algorithm for targeted property-based testing, so that it will find higher quality results more reliably. Specifically, in cases where it would previously have got near a local optimum, it will now tend to achieve the locally optimal value.- changes from version 4.54.1:
* This release is mostly internal changes in support of better testing of the core engine. You are unlikely to see much effect, although some internal heuristics have changed slightly.- changes from version 4.54.0:
* This release adds a dedicated phase for targeted property-based testing, and (somewhat) improves the targeting algorithm so that it will find higher quality results more reliably. This comes at a cost of making it more likely to get stuck in a local optimum.- changes from version 4.53.3:
* This patch fixes \"from_type()\" with \"typing.Hashable\" and \"typing.Sized\", which previously failed with an internal error on Python 3.7 or later.
* Thanks to Lea Provenzano for both reporting issue #2272 and writing the patch!
* Fri Dec 13 2019 Arun Persaud - update to version 4.53.2:
* This release reorganises a number of the Hypothesis internal modules into a package structure. If you are only depending on the public API it should have no effect. If you are depending on the internal API (which you shouldn’t be, and which we don’t guarantee compatibility on) you may have to rename some imports.- changes from version 4.53.1:
* This release changes the size distribution of the number of steps run in stateful testing: It will now almost always run the maximum number of steps permitted.- changes from version 4.53.0:
* Test Statistics now include the best score seen for each label, which can help avoid the threshold problem when the minimal example shrinks right down to the threshold of failure (issue [#2180]).- changes from version 4.52.0:
* This release changes the stateful_step_count setting to raise an error if set to 0. This is a backwards compatible change because a value of 0 would never have worked and attempting to run it would have resulted in an internal assertion error.- changes from version 4.51.1:
* This release makes a small internal change to the distribution of test cases. It is unlikely to have much user visible impact.- changes from version 4.51.0:
* This release deprecates use of AATTexample, AATTseed, or AATTreproduce_failure without AATTgiven.
* Sat Dec 07 2019 Arun Persaud - update to version 4.50.8:
* This patch makes certain uses of Bundles more efficient in stateful testing (issue #2078).- changes from version 4.50.7:
* This release refactors some of Hypothesis’s internal interfaces for representing data generation. It should have no user visible effect.- changes from version 4.50.6:
* This patch removes some old debugging helpers in our Numpy extra which have not been needed since issue #1963 and issue #2245.- changes from version 4.50.5:
* This patch fixes issue #2229, where Numpy arrays of unsized strings would only ever have strings of size one due to an interaction between our generation logic and Numpy’s allocation strategy.- changes from version 4.50.4:
* This patch fixes a rare internal error in strategies for a list of unique items sampled from a short non-unique sequence (issue [#2247]). The bug was discovered via hypothesis-jsonschema.- changes from version 4.50.3:
* This release improves the error message when AATTsettings tries to inherit settings from a parent argument that isn’t a settings instance.- changes from version 4.50.2:
* This release improves Hypothesis’s “Falsifying example” output, by breaking output across multiple lines where necessary, and by removing irrelevant information from the stateful testing output.- changes from version 4.50.1:
* This patch adds flake8-comprehensions to our linter suite. There is no user-visible change - expect perhaps via some strange microbenchmarks - but certain parts of the code now have a clear and more consistent style.- changes from version 4.50.0:
* This release fixes some cases where we might previously have failed to run the validation logic for some strategies. As a result tests which would previously have been silently testing significantly less than they should may now start to raise InvalidArgument now that these errors are caught.- changes from version 4.49.0:
* This release significantly improves the data distribution in rule based stateful testing , by using a technique called Swarm Testing (Groce, Alex, et al. “Swarm testing.” Proceedings of the 2012 International Symposium on Software Testing and Analysis. ACM, 2012.) to select which rules are run in any given test case. This should allow it to find many issues that it would previously have missed.
* This change is likely to be especially beneficial for stateful tests with large numbers of rules.- changes from version 4.48.1:
* This release adds some heuristics to test case generation that try to ensure that test cases generated early on will be relatively small.
* This fixes a bug introduced in Hypothesis 4.42.0 which would cause occasional too_slow failures on some tests.- changes from version 4.48.0:
* This release revokes the deprecation of find, as we’ve now rebuilt it on top of AATTgiven, which means it has minimal maintenance burden and we’re happy to support it.- changes from version 4.47.5:
* This release rebuilds find() on top of AATTgiven in order to have more code in common. It should have minimal user visible effect.- changes from version 4.47.4:
* This patch removes an internal compatibility shim that we no longer need.- changes from version 4.47.3:
* This patch fixes several typos in our docstrings and comments, with no change in behaviour. Thanks to Dmitry Dygalo for identifying and fixing them!- changes from version 4.47.2:
* This release fixes an internal issue where Hypothesis would sometimes generate test cases that were above its intended maximum size. This would only have happened rarely and probably would not have caused major problems when it did.
* Users of the new targeted property-based testing might see minor impact (possibly slightly faster tests and slightly worse target scores), but only in the unlikely event that they were hitting this problem. Other users should not see any effect at all.- changes from version 4.47.1:
* This release removes some unused code from the core engine. There is no user-visible change.- changes from version 4.47.0:
* This release commonizes some code between running explicit examples and normal test execution. The main user visible impact of this is that deadlines are now enforced when running explicit examples.
* Sat Nov 23 2019 Arun Persaud - update to version 4.46.1:
* This patch ensures that a KeyboardInterrupt received during example generation is not treated as a mystery test failure but instead propagates to the top level, not recording the interrupted generation in the conjecture data tree. Thanks to Anne Archibald for identifying and fixing the problem.- changes from version 4.46.0:
* This release changes the behaviour of floats() when excluding signed zeros - floats(max_value=0.0, exclude_max=True) can no longer generate -0.0 nor the much rarer floats(min_value=-0.0, exclude_min=True) generate +0.0.
* The correct interaction between signed zeros and exclusive endpoints was unclear; we now enforce the invariant that floats() will never generate a value equal to an excluded endpoint (issue [#2201]).
* If you prefer the old behaviour, you can pass floats(max_value=-0.0) or floats(min_value=0.0) which is exactly equivalent and has not changed. If you had two endpoints equal to zero, we recommend clarifying your tests by using just() or sampled_from() instead of floats().- changes from version 4.45.1:
* This patch improves the error message when invalid arguments are passed to rule() or invariant() (issue #2149). Thanks to Benjamin Palmer for this bugfix!- changes from version 4.45.0:
* This release supports typing.Final and typing.TypedDict in from_type().- changes from version 4.44.5:
* This patch disables our pytest plugin when running on versions of pytest before 4.3, the oldest our plugin supports. Note that at time of writing the Pytest developers only support 4.6 and later!
* Hypothesis tests using AATTgiven() work on any test runner, but our integrations to e.g. avoid example database collisions when combined with AATTpytest.mark.parametrize eventually drop support for obsolete versions.- changes from version 4.44.4:
* This patch adds some internal comments and clarifications to the Hypothesis implementation. There is no user-visible change.- changes from version 4.44.3:
* This patch avoids importing test runners such as :pypi`pytest`, :pypi`unittest2`, or :pypi`nose` solely to access their special “skip test” exception types - if the module is not in sys.modules, the exception can’t be raised anyway.
* This fixes a problem where importing an otherwise unused module could cause spurious errors due to import-time side effects (and possibly -Werror).- changes from version 4.44.2:
* This release fixes AATTgiven 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 AATTgiven.- changes from version 4.44.1:
* This patch allows Hypothesis to run in environments that do not specify a __file__, such as a zipapp (issue #2196).- changes from version 4.44.0:
* This release adds a gufunc argument to mutually_broadcastable_shapes() (issue #2174), which allows us to generate shapes which are valid for functions like numpy.matmul that require shapes which are not simply broadcastable.
* Thanks to everyone who has contributed to this feature over the last year, and a particular shout-out to Zac Hatfield-Dodds and Ryan Soklaski for mutually_broadcastable_shapes() and to Ryan Turner for the downstream hypothesis-gufunc project.- changes from version 4.43.9:
* This patch fixes issue #2108, where the first test using data() to draw from characters() or 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.- changes from version 4.43.8:
* This release ensures that the strategies passed to AATTgiven 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.- changes from version 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).- changes from version 4.43.6 :
* This patch refactors width handling in floats(); you may notice small performance improvements but the main purpose is to enable work on issue #1704 (improving shrinking of bounded floats).- changes from version 4.43.5 :
* This patch removes an unused internal flag. There is no user-visible change.- changes from version 4.43.4:
* This patch corrects the exception type and error message you get if you attempt to use data() to draw from something which is not a strategy. This never worked, but the error is more helpful now.- changes from version 4.43.3:
* We’ve adopted 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.- changes from version 4.43.2:
* This patch fixes the formatting of some documentation, but there is no change to any executed code.- changes from version 4.43.1 :
* Python 3.8’s new typing.Literal type - see PEP 586 for details - is now supported in from_type().- changes from version 4.43.0:
* This release adds the strategy 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 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).
* Thanks to Ryan Soklaski, Zac Hatfield-Dodds, and AATTrdturnermtl who contributed to this new feature.- changes from version 4.42.10:
* This release fixes from_type() when used with bounded or constrained 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.- changes from version 4.42.9:
* This patch ensures that the default value broadcastable_shapes() chooses for max_dims is always valid (at most 32), even if you pass min_dims=32.- changes from version 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).- changes from version 4.42.7:
* This patch makes stateful step printing expand the result of a step into multiple variables when you return multiple() (issue [#2139]). Thanks to Joseph Weston for reporting and fixing this bug!- changes from version 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.
* Thanks to Robert Knight for this bugfix!- changes from version 4.42.5:
* This patch corrects some internal documentation. There is no user-visible change.- changes from version 4.42.4:
* This release fixes a bug (issue #2160) where decorators applied after AATTsettings and before AATTgiven were ignored.
* Thanks to Tom Milligan for this bugfix!- changes from version 4.42.3:
* This release updates Hypothesis’s formatting to the new version of black, and has absolutely no user visible effect.- changes from version 4.42.2:
* This release fixes a bug in 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.- changes from version 4.42.1:
* Python 3.8’s new typing.SupportsIndex type - see PEP 357 for details - is now supported in from_type().
* Thanks to Grigorios Giannakopoulos for the patch!- changes from version 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 targeted property-based testing 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.- changes from version 4.41.3:
* This patch is to ensure that our internals remain comprehensible to mypy 0.740 - there is no user-visible change.- changes from version 4.41.2:
* This patch changes some internal hashes to SHA384, to better support users subject to FIPS-140. There is no user-visible API change.
* Thanks to Paul Kehrer for this contribution!- changes from version 4.41.1:
* This release makes --hypothesis-show-statistics much more useful for tests using a RuleBasedStateMachine, by simplifying the reprs so that events are aggregated correctly.- changes from version 4.41.0:
* This release upgrades the fixed_dictionaries() strategy to support optional keys (issue #1913).
* Wed Oct 16 2019 Marketa Calabkova - update to version 4.40.2
* Type hints improved
* Performance improved
* Array indexing improved
*
*
*experimental
*
* support for targeted property-based testing
* Sun Aug 25 2019 Arun Persaud - update to version 4.34.0:
* The from_type() strategy now knows to look up the subclasses of abstract types, which cannot be instantiated directly. This is very useful for hypothesmith to support libCST.- changes from version 4.33.1:
* This patch works around a crash when an incompatible version of Numpy is installed under PyPy 5.10 (Python 2.7).- changes from version 4.33.0:
* This release improves the domains() strategy, as well as the urls() and the 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.Thanks to TechDragon for this improvement.- changes from version 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 from_lark() with lark 0.7.2 and later.
* Sun Aug 04 2019 Arun Persaud - update to version 4.32.2:
* This patch updates some internal comments for mypy 0.720. There is no user-visible impact.- changes from version 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.- changes from version 4.32.0:
* This release makes 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 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).
* Sun Jul 28 2019 Arun Persaud - update to version 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.- changes from version 4.31.0 :
* This release simplifies the logic of the 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.
* Mon Jul 22 2019 Tomáš Chvátal - Update to 4.28.2:
* Various bugfixes and deprecations all around
* Sat Jun 08 2019 Arun Persaud - update to version 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. Thanks to Daniel Hahler for the patch, and Victor Stinner for his work on bpo-37032 that made it possible.