keyring changelog

Changelog History

Page 6

• v18.0.0 Changes

  February 13, 2019

  • 🍎 #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.

• v17.1.1 Changes

  December 23, 2018

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

• v17.1.0 Changes

  December 06, 2018

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

• v17.0.0 Changes

  • 🚚 #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".

• v16.1.1 Changes

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

• v16.1.0 Changes

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

• v16.0.2 Changes

  • 🏁 #319: In Windows backend, trap all exceptions when attempting to import pywin32.

• v16.0.1 Changes

  • #357: Once again allow all positive, non-zero priority keyrings to participate.

• v16.0.0 Changes

  • 🏁 #323: Fix race condition in delete_password on Windows.
  • #352: All suitable backends (priority 1 and greater) are allowed to participate.

• v15.2.0 Changes

  • #350: Added new API for get_credentials, for backends that can resolve both a username and password for a service.

• « First
• ‹ Prev
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• 10
• Next ›
• Last »