Log Message:
py-keyring: updated to 18.0.0

18.0.0
* 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
* Update packaging technique to avoid 0.0.0 releases.

17.1.0
* 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
* Remove application attribute from stored passwords
  using SecretService, addressing regression introduced in
  10.5.0. Impacted Linux keyrings will once again
  prompt for a password for "Python program".

16.1.1
* 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.

16.0.2
* In Windows backend, trap all exceptions when
  attempting to import pywin32.

16.0.1
* Once again allow all positive, non-zero priority
  keyrings to participate.

16.0.0
* Fix race condition in delete_password on Windows.
* All suitable backends (priority 1 and greater) are
  allowed to participate.

15.2.0
* Added new API for get_credentials, for backends
  that can resolve both a username and password for a service.

15.1.0
* Add the Null keyring, disabled by default.
* Added --disable option to command-line
  interface.
* Now honor a PYTHON_KEYRING_BACKEND
  environment variable to select a backend. Environments
  may set to keyring.backends.null.Keyring to disable
  keyring.