gh-102281: fix potential nullptr dereference + use of uninitialized memory#102282
gh-102281: fix potential nullptr dereference + use of uninitialized memory#102282corona10 merged 3 commits into
Conversation
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
corona10
left a comment
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
|
Thanks @maxbachmann for the PR, and @corona10 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry, something went wrong.
|
Thanks @maxbachmann for the PR, and @corona10 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Sorry, something went wrong.
|
Sorry, @maxbachmann and @corona10, I could not cleanly backport this to |
Sorry, something went wrong.
|
Sorry @maxbachmann and @corona10, I had trouble checking out the |
Sorry, something went wrong.
|
@corona10 will you do the backporting, or should I create the corresponding Pull Requests? |
Sorry, something went wrong.
Please create PRs for them :) |
Sorry, something went wrong.
|
@corona10 This does not need a backport for Python 3.10, since this issue was introduced in Python 3.11. |
Sorry, something went wrong.
edited by bedevere-bot
LoadingUh oh!
There was an error while loading. Please reload this page.
Copy link Copy MarkdownSorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.