Closed nedbat closed 5 years ago
Thanks! But this is not necessary. Your issue has been fixed in pypa/twine#421 but hasn't been released yet.
If it matters, I think I agree with @nedbat that even though it's fixed downstream seems unnecessary to warn twice here even if it's fixed downstream too.
I guess in some way it isn't necessary, but only because you know how this file is used in twine. Looked at in isolation, the file still has an annoying behavior: it has the exact same warning twice: once on import, and then again if the renderer is called. That seems unnecessary.
Sounds like you don't want this?
Turns out it was super simple.