For what its worth, providing backwards compatibility for this *user surfaced* configuration consists of doing this:
$ diff -u keyring/backend.py.smdist keyring/backend.py
--- /usr/share/pyshared/keyring/backend.py.smdist 2013-12-12 10:25:28.576780465 -0500
+++ /usr/share/pyshared/keyring/backend.py 2013-12-12 10:26:46.753677810 -0500
@@ -9,6 +9,7 @@
from keyring import errors
from keyring.util import properties
from keyring.py27compat import add_metaclass, filter
+from keyring.backends.file import PlaintextKeyring as UncryptedFileKeyring
import keyring.util
To be clear, your suggestion that you fixed all the packages in Ubuntu that might have used this is not sufficient to actually provide backwards compatibility.
I found this by using a package in ubuntu that previously worked and was broken after an upgrade.
For what its worth, providing backwards compatibility for this *user surfaced* configuration consists of doing this:
$ diff -u keyring/ backend. py.smdist keyring/backend.py pyshared/ keyring/ backend. py.smdist 2013-12-12 10:25:28.576780465 -0500 pyshared/ keyring/ backend. py 2013-12-12 10:26:46.753677810 -0500 backends. file import PlaintextKeyring as UncryptedFileKe yring
--- /usr/share/
+++ /usr/share/
@@ -9,6 +9,7 @@
from keyring import errors
from keyring.util import properties
from keyring.py27compat import add_metaclass, filter
+from keyring.
import keyring.util
To be clear, your suggestion that you fixed all the packages in Ubuntu that might have used this is not sufficient to actually provide backwards compatibility.
I found this by using a package in ubuntu that previously worked and was broken after an upgrade.