All Versions
124
Latest Version
Avg Release Cycle
37 days
Latest Release
-

Changelog History
Page 11

  • v3.0.4 Changes

    • Issue #114: Fix detection of pyfs under Mercurial Demand Import.

  • v3.0.3 Changes

    • Simplified the implementation of keyring.core.load_keyring. It now uses __import__ instead of loading modules explicitly. The keyring_path parameter to load_keyring is now deprecated. Callers should instead ensure their module is available on sys.path before calling load_keyring. Keyring still honors keyring-path. This change fixes Issue #113 in which the explicit module loading of keyring modules was breaking package-relative imports.

  • v3.0.2 Changes

    • 📇 Renamed keyring.util.platform to keyring.util.platform_. As reported in Issue #112 and mercurial_keyring #31 <https://bitbucket.org/Mekk/mercurial_keyring/issue/31>_ and in Mercurial itself <http://bz.selenic.com/show_bug.cgi?id=4029>_, Mercurial's Demand Import does not honor absolute_import directives, so it's not possible to have a module with the same name as another top-level module. A patch is in place to fix this issue upstream, but to support older Mercurial versions, this patch will remain for some time.

  • v3.0.1 Changes

    • Ensure that modules are actually imported even in Mercurial's Demand Import environment.

    3.0

    • ✂ Removed support for Python 2.5.
    • ✂ Removed names in keyring.backend moved in 1.1 and previously retained for compatibility.

  • v2.1.1 Changes

    • ⏪ Restored Python 2.5 compatibility (lost in 2.0).

    2.1

    • Issue #10: Added a 'store' attribute to the OS X Keyring, enabling custom instances of the KeyringBackend to use another store, such as the 'internet' store. For example::

      keys = keyring.backends.OS_X.Keyring() keys.store = 'internet' keys.set_password(system, user, password) keys.get_password(system, user)

    The default for all instances can be set in the class::

       keyring.backends.OS_X.Keyring.store = 'internet'

    • ⚠ GnomeKeyring: fix availability checks, and make sure the warning message from pygobject is not printed.

    • ✅ Fixes to GnomeKeyring and SecretService tests.

  • v2.0.3 Changes

    • Issue #112: Backend viability/priority checks now are more aggressive about module presence checking, requesting __name__ from imported modules to force the demand importer to actually attempt the import.

  • v2.0.2 Changes

    • 🏁 Issue #111: Windows backend isn't viable on non-Windows platforms.

  • v2.0.1 Changes

    • 🏁 Issue #110: Fix issues with Windows.RegistryKeyring.

    2.0

    • 👍 Issue #80: Prioritized backend support. The primary interface for Keyring backend classes has been refactored to now emit a 'priority' based on the current environment (operating system, libraries available, etc). These priorities provide an indication of the applicability of that backend for the current environment. Users are still welcome to specify a particular backend in configuration, but the default behavior should now be to select the most appropriate backend by default.

  • v1.6.1 Changes

    • ✅ Only include pytest-runner in 'setup requirements' when ptr invocation is indicated in the command-line (Issue #105).

    1.6

    • GNOME Keyring backend:

      • Use the same attributes (username / service) as the SecretService backend uses, allow searching for old ones for compatibility.
      • Also set application attribute.
      • Correctly handle all types of errors, not only CANCELLED and NO_MATCH.
      • Avoid printing warnings to stderr when GnomeKeyring is not available.

    • Secret Service backend:

      • Use a better label for passwords, the same as GNOME Keyring backend uses.

    1.5

    • SecretService: allow deleting items created using previous python-keyring versions.

    Before the switch to secretstorage, python-keyring didn't set "application" attribute. Now in addition to supporting searching for items without that attribute, python-keyring also supports deleting them.

    • 0️⃣ Use secretstorage.get_default_collection if it's available.

    On secretstorage 1.0 or later, python-keyring now tries to create the default collection if it doesn't exist, instead of just raising the error.

    • ✅ Improvements for tests, including fix for Issue #102.

    1.4

    • Switch GnomeKeyring backend to use native libgnome-keyring via GObject Introspection, not the obsolete python-gnomekeyring module.

    1.3

    • 👉 Use the SecretStorage library <https://pypi.python.org/pypi/SecretStorage>_ to implement the Secret Service backend (instead of using dbus directly). Now the keyring supports prompting for and deleting passwords. Fixes #69, #77, and #93.
    • Catch gnomekeyring.IOError per the issue reported in Nova client <https://bugs.launchpad.net/python-novaclient/+bug/1116302>_.
    • 👍 Issue #92 Added support for delete_password on Mac OS X Keychain.

  • v1.2.3 Changes

    • 🛠 Fix for Encrypted File backend on Python 3.
    • 👍 Issue #97 Improved support for PyPy.