Fix keyring support

[di]

Per this comment, fix a regression from #395 that would never successfully import keyring. A full explanation as to why this needed changed is in 3ae98ed.

Thanks to @adamtheturtle for catching it.

[codecov]

Codecov Report

Merging #408 into master will increase coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #408      +/-   ##
==========================================
+ Coverage   77.99%   78.08%   +0.09%     
==========================================
  Files          14       14              
  Lines         727      730       +3     
  Branches      104      104              
==========================================
+ Hits          567      570       +3     
  Misses        128      128              
  Partials       32       32

Impacted Files	Coverage Δ
twine/utils.py	84% <100%> (+0.39%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 49e88ce...5e80bfa. Read the comment docs.

[adamtheturtle]

Thank you @di and @theacodes - a release with this fix would be appreciated - is there anything I can do to help with that?

[jaraco]

This issue bit me today. I don't often release locally, but when I do, I do rely on keyring. I'll see if I can cut a release.

[jaraco]

I've updated the changelog and version, following patterns from prior commits, and tagged that commit. Unfortunately, I don't have access to upload to PyPI. Would @dstufft or @brainwane or @sigmavirus24 be willing to cut a release? Alternatively, add me to PyPI maintainers if you'd like me to upload the release.

[di]

@jaraco FYI, Sumana has stepped away as a twine maintainer.

[sigmavirus24]

@jaraco I'd also ask that you not push changes to this project like you've done. PRs are the project's preferred way of working. You pushed release notes that were premature

[jaraco]

@sigmavirus24 My mistake. I was working from the assumption that I had access to help cut releases, so I was seeking to do just that. Since nothing had changed between the last release and this bugfix, it seemed like a low risk bugfix release and I was seeking to get it out. I'll back out the changelog and delete the tag.

I was affected by this bug again today. It would be nice to get a fix out.