Merge #163

163: Scheduled weekly dependency update for week 42 r=mithrandi




## 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.
<table align="center">

<tr>
<td><b>cryptography</b></td>
<td align="center">2.0.3</td>
<td align="center">&raquo;</td>
<td align="center">2.1.1</td>
<td>
     <a href="https://pypi.python.org/pypi/cryptography">PyPI</a> | <a href="https://pyup.io/changelogs/cryptography/">Changelog</a> | <a href="https://github.com/pyca/cryptography">Repo</a> 

</td>

<tr>
<td><b>hypothesis</b></td>
<td align="center">3.31.2</td>
<td align="center">&raquo;</td>
<td align="center">3.33.0</td>
<td>
     <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> 

</td>

<tr>
<td><b>pyasn1-modules</b></td>
<td align="center">0.1.4</td>
<td align="center">&raquo;</td>
<td align="center">0.1.5</td>
<td>
     <a href="https://pypi.python.org/pypi/pyasn1-modules">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1-modules/">Changelog</a> | <a href="https://github.com/etingof/pyasn1-modules">Repo</a> 

</td>

<tr>
<td><b>pyasn1</b></td>
<td align="center">0.3.6</td>
<td align="center">&raquo;</td>
<td align="center">0.3.7</td>
<td>
     <a href="https://pypi.python.org/pypi/pyasn1">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1/">Changelog</a> | <a href="https://github.com/etingof/pyasn1">Repo</a> 

</td>

<tr>
<td><b>pyrsistent</b></td>
<td align="center">0.13.0</td>
<td align="center">&raquo;</td>
<td align="center">0.14.0</td>
<td>
     <a href="https://pypi.python.org/pypi/pyrsistent">PyPI</a> | <a href="https://pyup.io/changelogs/pyrsistent/">Changelog</a> | <a href="http://github.com/tobgu/pyrsistent/">Repo</a> 

</td>

</tr>
</table>



## 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 &lt;database&gt;` 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(&#39;Permissions&#39;, &#39;READ, WRITE, EXECUTE&#39;)`` 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 &lt;hypothesis.settings.use_coverage&gt;` 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&#39;s slower than on CPython, sometimes it&#39;s
>faster, but it&#39;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&#39;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! 🤖

requirements.txt

@@ -11,25 +11,25 @@ automat==0.6.0
 axiom==0.7.5
 characteristic==14.3.0
 constantly==15.1.0
-cryptography==2.0.3
+cryptography==2.1.1
 eliot==1.1.0
 enum34==1.1.6
 epsilon==0.7.1
 extras==1.0.0
 fixtures==3.0.0
 fusion-util==1.2.0
 hyperlink==17.3.1
-hypothesis==3.31.2
+hypothesis==3.33.0
 idna==2.6
 incremental==17.5.0
 ipaddress==1.0.18
 linecache2==1.0.0
 pbr==3.1.1
 py2casefold==0.2.1
-pyasn1-modules==0.1.4
-pyasn1==0.3.6
+pyasn1-modules==0.1.5
+pyasn1==0.3.7
 pyopenssl==17.3.0
-pyrsistent==0.13.0
+pyrsistent==0.14.0
 python-mimeparse==1.6.0
 service-identity==17.0.0
 six==1.11.0