GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||
GeezerVison is showing github.com — gh-87347: Fix PyObject_NEW() regression by vstinner · Pull Request #94234 · python/cpython Conversation
|
|
cc @corona10 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Unused macro?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks like leftovers from an early revision. I'm sure Victor will remove it before merging.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Oops, I forgot about it. That's why reviews are great :-) I removed this unused macro. I used if+goto instead of the macro.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Don't add parenthesis around the type parameter. Add unit tests on PyObject_NEW() and similar functions.
|
Merged, thanks for reviews! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Oops, my test leaks 4 references: I wrote PR #94330 to fix it. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.