bpo-41995 :fix five possible Null Pointer Dereference bugs.#22635
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
vstinner
left a comment
There was a problem hiding this comment.
Can you please write a separated PR for the tracemalloc fix? It should be backported up to 3.8, whereas the zoneinfo fix should only be backported up to 3.9. It's just more convenient to have two separated PR.
The tracemalloc fix is correct :-)
|
cc @pganssle for the zoneinfo fix ;-) |
|
|
Please add also a NEWS entry if this bug affects behavior and don't forget to sign the CLA. |
|
This PR is stale because it has been open for 30 days with no activity. |
Where to add NEWS entry? |
|
This PR is stale since October 2020. I prefer to merge it without document it rather than keeping the bugs. |
…ythonGH-22635) (cherry picked from commit f1ff800) Co-authored-by: Yunlongs <lylgood@foxmail.com>
|
GH-24261 is a backport of this pull request to the 3.9 branch. |
|
Oh, _tracemalloc was fixed in commit 66c28f5. |
fix five possible null pointer dereference bugs in https://bugs.python.org/issue41995.
https://bugs.python.org/issue41995