Scheduled weekly dependency update for week 46

[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.

attrs	17.2.0	»	17.3.0	PyPI | Changelog | Homepage
cryptography	2.1.2	»	2.1.3	PyPI | Changelog | Repo
hypothesis	3.33.0	»	3.37.0	PyPI | Changelog | Repo

Changelogs

attrs 17.2.0 -> 17.3.0

17.3.0

---

Backward-incompatible Changes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Attributes are not defined on the class body anymore.

This means that if you define a class C with an attribute x, the class will not have an attribute x for introspection anymore.
Instead of C.x, use attr.fields(C).x or look at C.__attrs_attrs__.
The old behavior has been deprecated since version 16.1.
(253 <https://github.com/python-attrs/attrs/issues/253>_)

Changes
^^^^^^^

• super() and __class__ now work on Python 3 when slots=True.
  (102 <https://github.com/python-attrs/attrs/issues/102>, 226 <https://github.com/python-attrs/attrs/issues/226>, 269 <https://github.com/python-attrs/attrs/issues/269>, 270 <https://github.com/python-attrs/attrs/issues/270>, 272 <https://github.com/python-attrs/attrs/issues/272>_)
• Added type argument to attr.ib() and corresponding type attribute to attr.Attribute.

This change paves the way for automatic type checking and serialization (though as of this release attrs does not make use of it).
In Python 3.6 or higher, the value of attr.Attribute.type can alternately be set using variable type annotations
(see PEP 526 <https://www.python.org/dev/peps/pep-0526/>). (151 <https://github.com/python-attrs/attrs/issues/151>, 214 <https://github.com/python-attrs/attrs/issues/214>, 215 <https://github.com/python-attrs/attrs/issues/215>, 239 <https://github.com/python-attrs/attrs/issues/239>_)

• The combination of str=True and slots=True now works on Python 2.
  (198 <https://github.com/python-attrs/attrs/issues/198>_)
• attr.Factory is hashable again. (204 <https://github.com/python-attrs/attrs/issues/204>_)
• Subclasses now can overwrite attribute definitions of their superclass.

That means that you can -- for example -- change the default value for an attribute by redefining it.
(221 <https://github.com/python-attrs/attrs/issues/221>, 229 <https://github.com/python-attrs/attrs/issues/229>)

• Added new option auto_attribs to attr.s that allows to collect annotated fields without setting them to attr.ib().

Setting a field to an attr.ib() is still possible to supply options like validators.
Setting it to any other value is treated like it was passed as attr.ib(default=value) -- passing an instance of attr.Factory also works as expected.
(262 <https://github.com/python-attrs/attrs/issues/262>, 277 <https://github.com/python-attrs/attrs/issues/277>)

• Instances of classes created using attr.make_class() can now be pickled.
  (282 <https://github.com/python-attrs/attrs/issues/282>_)

---

hypothesis 3.33.0 -> 3.37.0

3.37.0

---

This is a deprecation release for some health check related features.

The following are now deprecated:

• Passing :attr:~hypothesis.HealthCheck.exception_in_generation to
  :attr:~hypothesis.settings.suppress_health_check. This no longer does
  anything even when passed - All errors that occur during data generation
  will now be immediately reraised rather than going through the health check
  mechanism.
• Passing :attr:~hypothesis.HealthCheck.random_module to
  :attr:~hypothesis.settings.suppress_health_check. This hasn't done anything
  for a long time, but was never explicitly deprecated. Hypothesis always seeds
  the random module when running given tests, so this is no longer an error
  and suppressing it doesn't do anything.
• Passing non-:class:~hypothesis.HealthCheck values in
  :attr:~hypothesis.settings.suppress_health_check. This was previously
  allowed but never did anything useful.

In addition, passing a non-iterable value as :attr:~hypothesis.settings.suppress_health_check
will now raise an error immediately (it would never have worked correctly, but
it would previously have failed later). Some validation error messages have
also been updated.

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

---

3.36.1

---

This is a yak shaving release, mostly concerned with our own tests.

While :func:~python:inspect.getfullargspec was documented as deprecated
in Python 3.5, it never actually emitted a warning. Our code to silence
this (nonexistent) warning has therefore been removed.

We now run our tests with DeprecationWarning as an error, and made some
minor changes to our own tests as a result. This required similar upstream
updates to :pypi:coverage and :pypi:execnet (a test-time dependency via
:pypi:pytest-xdist).

There is no user-visible change in Hypothesis itself, but we encourage you
to consider enabling deprecations as errors in your own tests.

---

3.36.0

---

This release adds a setting to the public API, and does some internal cleanup:

• The :attr:~hypothesis.settings.derandomize setting is now documented (:issue:890)
• Removed - and disallowed - all 'bare excepts' in Hypothesis (:issue:953)
• Documented the :attr:~hypothesis.settings.strict setting as deprecated, and
  updated the build so our docs always match deprecations in the code.

---

3.35.0

---

This minor release supports constraining :func:~hypothesis.strategies.uuids
to generate :class:~python:uuid.UUIDs of a particular version.
(:issue:721)

Thanks to Dion Misic for this feature.

---

3.34.1

---

This patch updates the documentation to suggest
:func:builds(callable) <hypothesis.strategies.builds> instead of
:func:just(callable()) <hypothesis.strategies.just>.

---

3.34.0

---

Hypothesis now emits deprecation warnings if you apply
:func:given <hypothesis.given> more than once to a target.

Applying :func:given <hypothesis.given> repeatedly wraps the target multiple
times. Each wrapper will search the space of of possible parameters separately.
This is equivalent but will be much more inefficient than doing it with a
single call to :func:given <hypothesis.given>.

For example, instead of
given(booleans()) given(integers()), you could write
given(booleans(), integers())

---

3.33.1

---

This is a bugfix release:

• :func:~hypothesis.strategies.builds would try to infer a strategy for
  required positional arguments of the target from type hints, even if they
  had been given to :func:~hypothesis.strategies.builds as positional
  arguments (:issue:946). Now it only infers missing required arguments.
• An internal introspection function wrongly reported self as a required
  argument for bound methods, which might also have affected
  :func:~hypothesis.strategies.builds. Now it knows better.

---

That's it for now!

Happy merging! 🤖

---

This change is 

[codecov]

Codecov Report

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

@@          Coverage Diff          @@
##           master   #167   +/-   ##
=====================================
  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