Bump keyring from 10.4.0 to 19.0.2

[dependabot-preview]

Bumps keyring from 10.4.0 to 19.0.2.

Changelog

Sourced from keyring's changelog.

19.0.2

• Refresh package skeleton.
• Adopt black code style.

19.0.1

• Merge with 18.0.1.

18.0.1

• #386: ExceptionInfo no longer retains a reference to the traceback.

19.0.0

• #383: Drop support for EOL Python 2.7 - 3.4.

18.0.0

• #375: On macOS, the backend now raises a KeyringLocked when access to the keyring is denied (on get or set) instead of PasswordSetError or KeyringError. Any API users may need to account for this change, probably by catching the parent KeyringError. Additionally, the error message from the underying error is now included in any errors that occur.

17.1.1

• #368: Update packaging technique to avoid 0.0.0 releases.

17.1.0

• #366: When calling keyring.core.init_backend, if any limit function is supplied, it is saved and later honored by the ChainerBackend as well.

17.0.0

• #345: Remove application attribute from stored passwords using SecretService, addressing regression introduced in 10.5.0 (#292). Impacted Linux keyrings will once again prompt for a password for "Python program".

16.1.1

• #362: Fix error on import due to circular imports on Python 3.4.

16.1.0

• Refactor ChainerBackend, introduced in 16.0 to function as any other backend, activating when relevant.

... (truncated)

Commits

• 979f4dd Update changelog
• 135a9b3 Merge https://github.com/jaraco/tidelift
• b837ff5 Fade to black
• 8df6993 Merge https://github.com/jaraco/skeleton
• e8db26a Add support for automatic publishing of release notes
• 79733f0 Update skeleton documentation to reflect black adoption.
• d4c65e6 Use pytest-black-multipy to enable simple support for pytest-black where avai...
• 4399038 Only install and invoke pytest-black on Python 3
• 2fe1c20 Merge branch 'master' into feature/black
• 4186b77 Revert "Pin to pip 19.0 for now for pip 19.1 and develop mode (with pyproject.toml - build-backend present) pypa/pip#6434."
• 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #115.