You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This documentation is in the CHANGES.rst file, but it's impossible to use because it results in endless recursion between chainer.py's priority property and backends function.
Traceback (most recent call last):
File "", line 1, in
File "/build/repos/python-keyring/python-keyring/keyring/core.py", line 94, in init_backend
or max(
File "/build/repos/python-keyring/python-keyring/keyring/core.py", line 78, in recommended
return backend.priority >= 1
File "/build/repos/python-keyring/python-keyring/keyring/util/properties.py", line 26, in get
return self.fget.get(None, owner)()
File "/build/repos/python-keyring/python-keyring/keyring/backends/chainer.py", line 26, in priority
return 10 * (len(cls.backends) > 1)
File "/build/repos/python-keyring/python-keyring/keyring/util/properties.py", line 26, in get
return self.fget.get(None, owner)()
File "/build/repos/python-keyring/python-keyring/keyring/backends/chainer.py", line 39, in backends
return sorted(allowed, key=backend.by_priority, reverse=True)
File "/build/repos/python-keyring/python-keyring/keyring/backends/chainer.py", line 34, in
allowed = (
File "/build/repos/python-keyring/python-keyring/keyring/core.py", line 78, in recommended
return backend.priority >= 1
etc...
Expected behavior
restrict backends to only those 'recommended' (priority > 1)
The text was updated successfully, but these errors were encountered:
Describe the bug
This documentation is in the CHANGES.rst file, but it's impossible to use because it results in endless recursion between chainer.py's priority property and backends function.
To Reproduce
Steps to reproduce the behavior:
import keyring
keyring.core.init_backend(keyring.core.recommended)
etc...
Expected behavior
restrict backends to only those 'recommended' (priority > 1)
The text was updated successfully, but these errors were encountered: