build(deps): bump attrs from 19.3.0 to 20.2.0

[dependabot]

Bumps attrs from 19.3.0 to 20.2.0.

Release notes

Sourced from attrs's releases.

20.2.0

Backward-incompatible Changes

• attr.define(), attr.frozen(), attr.mutable(), and attr.field() remain provisional.

  This release fixes a bunch of bugs and ergonomics but they remain mostly unchanged.

  If you wish to use them together with mypy, you can simply drop this plugin into your project.

  Feel free to provide feedback to them in the linked issue #668.

  We will release the attrs namespace once we have the feeling that the APIs have properly settled. #668

Changes

• attr.define() et al now correct detect __eq__ and __ne__. #671

• attr.define() et al's hybrid behavior now also works correctly when arguments are passed. #675

• It's possible to define custom __setattr__ methods on slotted classes again. #681

• In 20.1.0 we introduced the inherited attribute on the attr.Attribute class to differentiate attributes that have been inherited and those that have been defined directly on the class.

  It has shown to be problematic to involve that attribute when comparing instances of attr.Attribute though, because when sub-classing, attributes from base classes are suddenly not equal to themselves in a super class.

  Therefore the inherited attribute will now be ignored when hashing and comparing instances of attr.Attribute. #684

• zope.interface is now a "soft dependency" when running the test suite; if zope.interface is not installed when running the test suite, the interface-related tests will be automatically skipped. #685

• The ergonomics of creating frozen classes using @define(frozen=True) and sub-classing frozen classes has been improved: you don't have to set on_setattr=None anymore. #687

20.1.0

Backward-incompatible Changes

• Python 3.4 is not supported anymore. It has been unsupported by the Python core team for a while now, its PyPI downloads are negligible, and our CI provider removed it as a supported option.

  It's very unlikely that attrs will break under 3.4 anytime soon, which is why we do not block its installation on Python 3.4. But we don't test it anymore and will block it once someone reports breakage. #608

Deprecations

• Less of a deprecation and more of a heads up: the next release of attrs will introduce an attrs namespace. That means that you'll finally be able to run import attrs with new functions that aren't cute abbreviations and that will carry better defaults.

  This should not break any of your code, because project-local packages have priority before installed ones. If this is a problem for you for some reason, please report it to our bug tracker and we'll figure something out.

  The old attr namespace isn't going anywhere and its defaults are not changing -- this is a purely additive measure. Please check out the linked issue for more details.

... (truncated)

Changelog

Sourced from attrs's changelog.

20.2.0 (2020-09-05)

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

• attr.define(), attr.frozen(), attr.mutable(), and attr.field() remain provisional.

  This release fixes a bunch of bugs and ergonomics but they remain mostly unchanged.

  If you wish to use them together with mypy, you can simply drop this plugin <https://gist.github.com/hynek/1e3844d0c99e479e716169034b5fa963#file-attrs_ng_plugin-py>_ into your project.

  Feel free to provide feedback to them in the linked issue #668.

  We will release the attrs namespace once we have the feeling that the APIs have properly settled. [#668](https://github.com/python-attrs/attrs/issues/668) <https://github.com/python-attrs/attrs/issues/668>_

Changes ^^^^^^^

• attr.define() et al now correct detect __eq__ and __ne__. [#671](https://github.com/python-attrs/attrs/issues/671) <https://github.com/python-attrs/attrs/issues/671>_

• attr.define() et al's hybrid behavior now also works correctly when arguments are passed. [#675](https://github.com/python-attrs/attrs/issues/675) <https://github.com/python-attrs/attrs/issues/675>_

• It's possible to define custom __setattr__ methods on slotted classes again. [#681](https://github.com/python-attrs/attrs/issues/681) <https://github.com/python-attrs/attrs/issues/681>_

• In 20.1.0 we introduced the inherited attribute on the attr.Attribute class to differentiate attributes that have been inherited and those that have been defined directly on the class.

  It has shown to be problematic to involve that attribute when comparing instances of attr.Attribute though, because when sub-classing, attributes from base classes are suddenly not equal to themselves in a super class.

  Therefore the inherited attribute will now be ignored when hashing and comparing instances of attr.Attribute. [#684](https://github.com/python-attrs/attrs/issues/684) <https://github.com/python-attrs/attrs/issues/684>_

• zope.interface is now a "soft dependency" when running the test suite; if zope.interface is not installed when running the test suite, the interface-related tests will be automatically skipped. [#685](https://github.com/python-attrs/attrs/issues/685) <https://github.com/python-attrs/attrs/issues/685>_

• The ergonomics of creating frozen classes using @define(frozen=True) and sub-classing frozen classes has been improved: you don't have to set on_setattr=None anymore. [#687](https://github.com/python-attrs/attrs/issues/687) <https://github.com/python-attrs/attrs/issues/687>_

---

20.1.0 (2020-08-20)

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

• Python 3.4 is not supported anymore.

... (truncated)

Commits

• 4f74fba Prepare 20.2.0
• 74605de Elaborate more on #684
• ea04c15 Drop superfluous word
• 060d1ef Add newsfragment on state of NG APIs
• c454722 Fix typo
• 504eefe NG: make frozen classes comfortably subclassable (#687)
• 4875590 Don't reset custom setattr in slotted classes (#681)
• bfd7bb4 Ignore inherited field when comparing Attributes (#684)
• dfb2ee2 Make zope a semi-optional test dependency (#685)
• 00c1c2c Add check-toml hook
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #156.