Skip to content

[3.8] bpo-41654: Explicitly cast PyExc_MemoryError to PyTypeObject to avoid warning #22102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pablogsal merged 1 commit into from
Sep 5, 2020
Merged

[3.8] bpo-41654: Explicitly cast PyExc_MemoryError to PyTypeObject to avoid warning #22102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
bpo-41654: Explicitly cast PyExc_MemoryError to PyTypeObject to avoid… 
… warning
  • Loading branch information
@pablogsal
pablogsal committed Sep 5, 2020
commit 2a2c0500ca617fd459576d8b2a51f9e0bd04ebaf
5 changes: 3 additions & 2 deletions Objects/exceptions.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2295,8 +2295,9 @@ MemoryError_dealloc(PyBaseExceptionObject *self)
{
BaseException_clear(self);

if (Py_TYPE(self) != PyExc_MemoryError) {
return Py_TYPE(self)->tp_free((PyObject *)self);
if (Py_TYPE(self) != (PyTypeObject *)PyExc_MemoryError) {
Py_TYPE(self)->tp_free((PyObject *)self);
return;
}

_PyObject_GC_UNTRACK(self);
Expand Down