jaraco: here's the first cut on a decent encrypted file backend: https://github.com/frispete/keyrings.cryptfile
I would be glad, if you could look on the namespace stuff
I'm using local file and file_base modules for now - will fix that later on
While at it, I've tried to cope with the base64.{de,en}codestring deprecation - how would you handle this?
Basically, the namespace stuff looks fine as does the base64 compatibility fallback.
You may want to consider removing the ‘wheel’ stuff from setup.py as well, as that’s what I’ve done in my project skeleton (which will update my projects as they get new releases).
see https://github.com/jaraco/skeleton for details
Hi jaraco, may I kindly ask you to look into an testing issue of my code? Altrough I call a method explicitely here https://github.com/frispete/keyrings.cryptfile/blob/master/tests/test_cryptfile.py#L38, the code is marked as not covered?!?
testing with: pytest -v --cov-config .coveragerc --cov-report term-missing --cov=keyrings/cryptfile
Name Stmts Miss Cover Missing
keyrings/cryptfile/cryptfile.py 84 18 79% 140-164, 173-180
_check_file calls _check_scheme and _check_version (if that wouldn't work, the complete machinery would fail..)
Let me know, what you think about mergability and if this moves in the right direction
I used the
tuple(set()) syntax because I prefer to assign variables in as few places as possible, but your fix is fine. Care to tag 10.3.1 (annotated) to cut the release?