Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update keyring to 13.0.0 #31

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Collaborator

This PR updates keyring from 12.0.1 to 13.0.0.

Changelog

13.0.0

------

* 327: In kwallet backend, if the collection or item is
locked, a ``KeyringLocked`` exception is raised. Clients
expecting a None response from ``get_password`` under
this condition will need to catch this exception.
Additionally, an ``InitError`` is now raised if the
connection cannot be established to the DBus.

* 298: In kwallet backend, when checking an existing
handle, verify that it is still valid or create a new
connection.

12.2.1

------

* Fixed issue in SecretService. Ref 226.

12.2.0

------

* 322: Fix AttributeError when ``escape.__builtins__``
is a dict.

* Deprecated ``keyring.util.escape`` module. If you use
this module or encounter the warning (on the latest
release of your packages), please `file a ticket
<https://github.com/jaraco/keyring/issues/new>`_.

12.1.0

------

* Unpin SecretStorage on Python 3.5+. Requires that
Setuptools 17.1 be used. Note that the special
handling will be unnecessary once Pip 9 can be
assumed (as it will exclude SecretStorage 3 in
non-viable environments).

12.0.2

------

* Pin SecretStorage to 2.x.
Links

@pyup-bot pyup-bot mentioned this pull request Jun 17, 2018
@coveralls
Copy link

coveralls commented Jun 17, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling e428323 on pyup-update-keyring-12.0.1-to-13.0.0 into 8365592 on master.

@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #32

@pyup-bot pyup-bot closed this Jun 25, 2018
@bpeterso2000 bpeterso2000 deleted the pyup-update-keyring-12.0.1-to-13.0.0 branch June 25, 2018 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants