by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 08 08:20
    ustauss opened #454
  • Aug 04 04:00
    AndrewGrossman commented #445
  • Aug 02 22:52

    jaraco on master

    Ensure virtualenv is upgraded w… Run tests on prereleases of Pyt… Add workaround for python/mypy#… and 5 more (compare)

  • Aug 02 21:49

    jaraco on v21.3.0

    Ensure virtualenv is upgraded w… Run tests on prereleases of Pyt… Add workaround for python/mypy#… and 4 more (compare)

  • Aug 02 21:48
    jaraco commented #445
  • Aug 02 21:41
    jaraco commented #447
  • Aug 02 21:32

    jaraco on master

    Add sagecipher to 3rd-party bac… Merge pull request #444 from p-… (compare)

  • Aug 02 21:32
    jaraco closed #444
  • Aug 02 21:27

    jaraco on master

    Update hyperlink to point to Gi… Merge branch 'master' of https:… Upadte changelog. Ref #440. (compare)

  • Aug 02 21:20

    jaraco on master

    Use correct XDG default for XDG… Merge pull request #440 from jn… (compare)

  • Aug 02 21:20
    jaraco closed #440
  • Aug 02 21:20
    jaraco commented #440
  • Jul 31 23:23
    tjslezak commented #449
  • Jul 31 22:57
    tjslezak commented #449
  • Jul 31 22:56
    tjslezak commented #449
  • Jul 31 22:56
    tjslezak commented #449
  • Jul 31 22:56
    tjslezak commented #449
  • Jul 31 22:55
    tjslezak commented #449
  • Jul 31 22:55
    tjslezak commented #449
  • Jul 30 07:21
    kdw27501 commented #286
Jason R. Coombs
@jaraco
mitya57: I’ve added you as collaborator on the keyring project. Do let me know if that doesn’t give you access to close #236. I’d like you to feel free to commit/approve/release issues relating to Linux.
Dmitry Shachnev
@mitya57
Looks like I can close the issues. Thanks!
Hans-Peter Jansen
@frispete
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?
Jason R. Coombs
@jaraco
Grr. I just typed up a message and because I was offline, Gitter discarded it.
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).
Hans-Peter Jansen
@frispete
jaraco: Thanks, done that now.
Hans-Peter Jansen
@frispete
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..)
Jason R. Coombs
@jaraco
@frispete: Nothing jumps out at me immediately. Maybe add a pdb.set_trace() at the code that’s apparently not being covered to determine if it’s indeed being called?
Hans-Peter Jansen
@frispete
found and fixed it... The tests still clutter the /tmp dir. Will address this in a later revision.
Let me know, what you think about mergability and if this moves in the right direction
Dmitry Shachnev
@mitya57
@jaraco I fixed the TypeError in keyring which made it unusable, hope you don’t mind.
Jason R. Coombs
@jaraco
@mitya57 I don’t mind. Thanks.
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?
Dmitry Shachnev
@mitya57
Done!
Jason R. Coombs
@jaraco
Awesome. Thanks!