Merge #155

155: Scheduled weekly dependency update for week 36 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>hypothesis</b></td>
<td align="center">3.22.0</td>
<td align="center">&raquo;</td>
<td align="center">3.23.2</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>pyrsistent</b></td>
<td align="center">0.12.3</td>
<td align="center">&raquo;</td>
<td align="center">0.13.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


### hypothesis 3.22.0 -> 3.23.2

>### 3.23.2

>-------------------

>This is a small refactoring release that removes a now-unused parameter to an
>internal API. It shouldn&#39;t have any user visible effect.

>-------------------


>### 3.23.1

>-------------------

>Hypothesis no longer propagates the dynamic scope of settings into strategy
>definitions.

>This release is a small change to something that was never part of the public
>API and you will almost certainly not notice any effect unless you&#39;re doing
>something surprising, but for example the following code will now give a
>different answer in some circumstances:

>.. code-block:: python

>    import hypothesis.strategies as st
>    from hypothesis import settings

>    CURRENT_SETTINGS = st.builds(lambda: settings.default)

>(We don&#39;t actually encourage you writing code like this)

>Previously this would have generated the settings that were in effect at the
>point of definition of ``CURRENT_SETTINGS``. Now it will generate the settings
>that are used for the current test.

>It is very unlikely to be significant enough to be visible, but you may also
>notice a small performance improvement.

>-------------------


>### 3.23.0

>-------------------

>This release adds a ``unique`` argument to :func:`~hypothesis.extra.numpy.arrays`
>which behaves the same ways as the corresponding one for
>:func:`~hypothesis.strategies.lists`, requiring all of the elements in the
>generated array to be distinct.

>-------------------


>### 3.22.2

>-------------------

>This release fixes an issue where Hypothesis would raise a ``TypeError`` when
>using the datetime-related strategies if running with ``PYTHONOPTIMIZE=2``.
>This bug was introduced in v3.20.0.  (See :issue:`822`)

>-------------------


>### 3.22.1

>-------------------

>Hypothesis now transparently handles problems with an internal unicode cache,
>including file truncation or read-only filesystems (:issue:`767`).
>Thanks to Sam Hames for the patch.

>-------------------






### pyrsistent 0.12.3 -> 0.13.0

>### 0.13.0

> * Fix 113, Skip field factories when loading pickled objects. There is a
>   minor backwards incompatibilty in the behaviour because of this. Thanks
>   teepark for fi this!
> * Fix 116, negative indexing for pdeques. Thanks Julian for this!










That's it for now!

Happy merging! 🤖

requirements.txt

@@ -19,7 +19,7 @@ extras==1.0.0
 fixtures==3.0.0
 fusion-util==1.2.0
 hyperlink==17.3.1
-hypothesis==3.22.0
+hypothesis==3.23.2
 idna==2.6
 incremental==17.5.0
 ipaddress==1.0.18
@@ -29,7 +29,7 @@ py2casefold==0.2.1
 pyasn1-modules==0.1.1
 pyasn1==0.3.3
 pyopenssl==17.2.0
-pyrsistent==0.12.3
+pyrsistent==0.13.0
 python-mimeparse==1.6.0
 service-identity==17.0.0
 six==1.10.0