Skip to content

bpo-40170: Always define PyExceptionClass_Name as a function #24553

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
vstinner merged 2 commits into from
Feb 17, 2021
Merged

bpo-40170: Always define PyExceptionClass_Name as a function #24553

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e726c39
bpo-40170: Remove macro variant of PyExceptionClass_Name
Feb 16, 2021
7e6e8d1
Add NEWS entry
Feb 16, 2021
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
Prev Previous commit
Add NEWS entry
  • Loading branch information
Erlend E. Aasland
Erlend E. Aasland committed Feb 16, 2021
commit 7e6e8d1edefd8eec89f4d3cbf1607a44d57fbfe8
3 changes: 3 additions & 0 deletions Misc/NEWS.d/next/C API/2021-02-16-22-29-39.bpo-40170.ahHmOo.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
:c:func:`PyExceptionClass_Name` is now always declared as a function, in
order to hide implementation details. The macro accessed
:c:member:`PyTypeObject.tp_name` directly. Patch by Erlend E. Aasland.