Scheduled weekly dependency update for week 42

[pyup-bot]

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.

cryptography	2.0.3	»	2.1.1	PyPI | Changelog | Repo
hypothesis	3.31.2	»	3.33.0	PyPI | Changelog | Repo
pyasn1-modules	0.1.4	»	0.1.5	PyPI | Changelog | Repo
pyasn1	0.3.6	»	0.3.7	PyPI | Changelog | Repo
pyrsistent	0.13.0	»	0.14.0	PyPI | Changelog | Repo

Changelogs

cryptography 2.0.3 -> 2.1.1

2.1

• FINAL DEPRECATION Python 2.6 support is deprecated, and will be removed
  in the next release of cryptography.
• BACKWARDS INCOMPATIBLE: Whirlpool, RIPEMD160, and
  UnsupportedExtension have been removed in accordance with our
  :doc:/api-stability policy.
• BACKWARDS INCOMPATIBLE: :attr:~cryptography.x509.DNSName.value,
  :attr:~cryptography.x509.RFC822Name.value, and
  :attr:~cryptography.x509.UniformResourceIdentifier.value will now return
  an :term:A-label string when parsing a certificate containing an
  internationalized domain name (IDN) or if the caller passed a :term:U-label
  to the constructor. See below for additional deprecations related to this
  change.
• Installing cryptography now requires pip 6 or newer.
• Deprecated passing :term:U-label strings to the
  :class:~cryptography.x509.DNSName,
  :class:~cryptography.x509.UniformResourceIdentifier, and
  :class:~cryptography.x509.RFC822Name constructors. Instead, users should
  pass values as :term:A-label strings with idna encoding if necessary.
  This change will not affect anyone who is not processing internationalized
  domains.
• Added support for
  :class:~cryptography.hazmat.primitives.ciphers.algorithms.ChaCha20. In
  most cases users should choose
  :class:~cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305
  rather than using this unauthenticated form.
• Added :meth:~cryptography.x509.CertificateRevocationList.is_signature_valid
  to :class:~cryptography.x509.CertificateRevocationList.
• Support :class:~cryptography.hazmat.primitives.hashes.BLAKE2b and
  :class:~cryptography.hazmat.primitives.hashes.BLAKE2s with
  :class:~cryptography.hazmat.primitives.hmac.HMAC.
• Added support for
  :class:~cryptography.hazmat.primitives.ciphers.modes.XTS mode for
  AES.
• Added support for using labels with
  :class:~cryptography.hazmat.primitives.asymmetric.padding.OAEP when using
  OpenSSL 1.0.2 or greater.
• Improved compatibility with NSS when issuing certificates from an issuer
  that has a subject with non-UTF8String string types.
• Add support for the :class:~cryptography.x509.DeltaCRLIndicator extension.
• Add support for the :class:~cryptography.x509.TLSFeature
  extension. This is commonly used for enabling OCSP Must-Staple in
  certificates.
• Add support for the :class:~cryptography.x509.FreshestCRL extension.

.. _v2-0-3:

hypothesis 3.31.2 -> 3.33.0

3.33.0

---

This release supports strategy inference for more field types in Django
:func:~hypothesis.extra.django.models - you can now omit an argument for
Date, Time, Duration, Slug, IP Address, and UUID fields. (:issue:642)

Strategy generation for fields with grouped choices now selects choices from
each group, instead of selecting from the group names.

---

3.32.2

---

This patch removes the mergedb tool, introduced in Hypothesis 1.7.1
on an experimental basis. It has never actually worked, and the new
:doc:Hypothesis example database <database> is designed to make such a
tool unnecessary.

---

3.32.1

---

This patch has two improvements for strategies based on enumerations.

• :func:~hypothesis.strategies.from_type now handles enumerations correctly,
  delegating to :func:~hypothesis.strategies.sampled_from. Previously it
  noted that Enum.__init__ has no required arguments and therefore delegated
  to :func:~hypothesis.strategies.builds, which would subsequently fail.
• When sampling from an :class:python:enum.Flag, we also generate combinations
  of members. Eg for Flag('Permissions', 'READ, WRITE, EXECUTE') we can now
  generate, Permissions.READ, Permissions.READ|WRITE, and so on.

---

3.32.0

---

This changes the default value of
:attr:use_coverage=True <hypothesis.settings.use_coverage> to True when
running on pypy (it was already True on CPython).

It was previously set to False because we expected it to be too slow, but
recent benchmarking shows that actually performance of the feature on pypy is
fairly acceptable - sometimes it's slower than on CPython, sometimes it's
faster, but it's generally within a factor of two either way.

---

3.31.6

---

This patch improves the quality of strategies inferred from Numpy dtypes:

• Integer dtypes generated examples with the upper half of their (non-sign) bits
  set to zero. The inferred strategies can now produce any representable integer.
• Fixed-width unicode- and byte-string dtypes now cap the internal example
  length, which should improve example and shrink quality.
• Numpy arrays can only store fixed-size strings internally, and allow shorter
  strings by right-padding them with null bytes. Inferred string strategies
  no longer generate such values, as they can never be retrieved from an array.
  This improves shrinking performance by skipping useless values.

This has already been useful in Hypothesis - we found an overflow bug in our
Pandas support, and as a result :func:~hypothesis.extra.pandas.indexes and
:func:~hypothesis.extra.pandas.range_indexes now check that min_size
and max_size are at least zero.

---

3.31.5

---

This release fixes a performance problem in tests where
:attr:~hypothesis.settings.use_coverage is set to True.

Tests experience a slow-down proportionate to the amount of code they cover.
This is still the case, but the factor is now low enough that it should be
unnoticeable. Previously it was large and became much larger in 3.28.4.

---

3.31.4

---

:func:~hypothesis.strategies.from_type failed with a very confusing error
if passed a :func:~python:typing.NewType (:issue:901). These psudeo-types
are now unwrapped correctly, and strategy inference works as expected.

---

3.31.3

---

This release makes some small optimisations to our use of coverage that should
reduce constant per-example overhead. This is probably only noticeable on
examples where the test itself is quite fast. On no-op tests that don't test
anything you may see up to a fourfold speed increase (which is still
significantly slower than without coverage). On more realistic tests the speed
up is likely to be less than that.

---

pyrsistent 0.13.0 -> 0.14.0

0.14.0

• Fix 117, pmap now accepts iterators as input to constructor. Thanks Julian for this!
• Drop support for Python 2.6. Nothing has been done in this release that will explicitly
  break pyrsistent for 2.6 but it will not be considered moving forward. Dropping 2.6
  support is the reason for stepping the second decimal instead of the third.

That's it for now!

Happy merging! 🤖

---

This change is 

[codecov]

Codecov Report

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

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

[mithrandi]

bors r+

[bors-fusion]

Build succeeded

• continuous-integration/travis-ci/push