Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled weekly dependency update for week 52 #173

Closed
wants to merge 5 commits into from

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Dec 25, 2017

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

asn1crypto 0.23.0 » 0.24.0 PyPI | Changelog | Repo
hypothesis 3.40.1 » 3.44.4 PyPI | Changelog | Repo
ipaddress 1.0.18 » 1.0.19 PyPI | Repo
pyrsistent 0.14.1 » 0.14.2 PyPI | Changelog | Repo
toolz 0.8.2 » 0.9.0 PyPI | Repo

Changelogs

asn1crypto 0.23.0 -> 0.24.0

0.24.0

  • x509.Certificate().self_signed will no longer return "yes" under any
    circumstances. This helps prevent confusion since the library does not
    verify the signature. Instead a library like oscrypto should be used
    to confirm if a certificate is self-signed.
  • Added various OIDs to x509.KeyPurposeId()
  • Added x509.Certificate().private_key_usage_period_value
  • Added structures for parsing common subject directory attributes for
    X.509 certificates, including x509.SubjectDirectoryAttribute()
  • Added algos.AnyAlgorithmIdentifier() for situations where an
    algorithm identifier may contain a digest, signed digest or encryption
    algorithm OID
  • Fixed a bug with x509.Certificate().subject_directory_attributes_value
    not returning the correct value
  • Fixed a bug where explicitly-tagged fields in a core.Sequence() would
    not function properly when the field had a default value
  • Fixed a bug with type checking in pem.armor()

hypothesis 3.40.1 -> 3.44.4

3.44.4


This release fixes :issue:1044, which slowed tests by up to 6%
due to broken caching.


3.44.3


This release improves the shrinker in cases where examples drawn earlier can
affect how much data is drawn later (e.g. when you draw a length parameter in
a composite and then draw that many elements). Examples found in cases like
this should now be much closer to minimal.


3.44.2


This is a pure refactoring release which changes how Hypothesis manages its
set of examples internally. It should have no externally visible effects.


3.44.1


This release fixes :issue:997, in which under some circumstances the body of
tests run under Hypothesis would not show up when run under coverage even
though the tests were run and the code they called outside of the test file
would show up normally.


3.44.0


This release adds a new feature: The :ref:reproduce_failure <reproduce_failure>,
designed to make it easy to use Hypothesis's binary format for examples to
reproduce a problem locally without having to share your example database
between machines.

This also changes when seeds are printed:

  • They will no longer be printed for
    normal falsifying examples, as there are now adequate ways of reproducing those
    for all cases, so it just contributes noise.
  • They will once again be printed when reusing examples from the database, as
    health check failures should now be more reliable in this scenario so it will
    almost always work in this case.

This work was funded by Smarkets <https://smarkets.com/>_.


3.43.1


This release fixes a bug with Hypothesis's database management - examples that
were found in the course of shrinking were saved in a way that indicated that
they had distinct causes, and so they would all be retried on the start of the
next test. The intended behaviour, which is now what is implemented, is that
only a bounded subset of these examples would be retried.


3.43.0


:exc:~hypothesis.errors.HypothesisDeprecationWarning now inherits from
:exc:python:FutureWarning instead of :exc:python:DeprecationWarning,
as recommended by :pep:565 for user-facing warnings (:issue:618).
If you have not changed the default warnings settings, you will now see
each distinct :exc:~hypothesis.errors.HypothesisDeprecationWarning
instead of only the first.


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.


3.41.0


:func:~hypothesis.strategies.sampled_from can now sample from
one-dimensional numpy ndarrays. Sampling from multi-dimensional
ndarrays still results in a deprecation warning. Thanks to Charlie
Tanksley for this patch.


pyrsistent 0.14.1 -> 0.14.2

0.14.2

  • Fix 121, regression in PClass.set() introduced in 0.14.1.

That's it for now!

Happy merging! 🤖


This change is Reviewable

Verified

This commit was signed with the committer’s verified signature. The key has expired.
tvdeyen Thomas von Deyen

Verified

This commit was signed with the committer’s verified signature. The key has expired.
tvdeyen Thomas von Deyen

Verified

This commit was signed with the committer’s verified signature. The key has expired.
tvdeyen Thomas von Deyen

Verified

This commit was signed with the committer’s verified signature. The key has expired.
tvdeyen Thomas von Deyen

Verified

This commit was signed with the committer’s verified signature. The key has expired.
tvdeyen Thomas von Deyen
@codecov
Copy link

codecov bot commented Dec 25, 2017

Codecov Report

Merging #173 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #173   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           7      7           
  Lines         187    187           
  Branches       14     14           
=====================================
  Hits          187    187

@pyup-bot
Copy link
Contributor Author

pyup-bot commented Jan 1, 2018

Closing this in favor of #174

@pyup-bot pyup-bot closed this Jan 1, 2018
@mithrandi mithrandi deleted the pyup-scheduled-update-12-25-2017 branch January 1, 2018 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant