bpo-41056: Fix a possible MemoryError leak within zoneinfo.#21007
bpo-41056: Fix a possible MemoryError leak within zoneinfo.#21007miss-islington merged 4 commits into
Conversation
This was detected by coverity as a REVERSE_INULL issue.
Coverity CID 1464644
|
I don't have time to look at this in any detail until tomorrow, but I think @tiran made essentially the same patch in #21003. That one got here first, but this one has a news entry. Looks simple enough, though, if y'all want to decide which patch to move forward with, the fact that you both came up with the exact same solution is probably a good enough "review". 😛 |
Sorry, something went wrong.
|
Thanks @gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9. |
Sorry, something went wrong.
|
Sorry @gpshead, I had trouble checking out the |
Sorry, something went wrong.
…thonGH-21007) This was detected by our Coverity scan as a REVERSE_INULL issue. Automerge-Triggered-By: @gpshead (cherry picked from commit d780fa7) Co-authored-by: Gregory P. Smith <greg@krypto.org>
This was detected by our Coverity scan as a REVERSE_INULL issue.
https://bugs.python.org/issue41056
Automerge-Triggered-By: @gpshead