Skip to content

gh-124520: What's New entry for ctypes metaclass __new__/__init__ change #124546

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
encukou merged 2 commits into from
Sep 27, 2024
Merged

gh-124520: What's New entry for ctypes metaclass __new__/__init__ change #124546

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6d94626
gh-124520: What's New for ctypes metaclass __new__/__init__ change
encukou Sep 25, 2024
b84f740
Call the metaclass, not just __new__
encukou Sep 25, 2024
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
Next Next commit
gh-124520: What's New for ctypes metaclass __new__/__init__ change
  • Loading branch information
@encukou
encukou committed Sep 25, 2024
commit 6d9462686124d0310777c5e9056b40c864a368d7
13 changes: 13 additions & 0 deletions Doc/whatsnew/3.13.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -824,6 +824,19 @@ copy
(Contributed by Serhiy Storchaka in :gh:`108751`.)


ctypes
------

* As a consequence of necessary internal refactoring, initialization of
internal metaclasses now happens in ``__init__`` rather
than in ``__new__``. This affects projects that subclass these internal
metaclasses to provide custom initialization.
Generally, logic that was done in ``__new__`` after calling
``super().__new__`` should be moved to ``__init__``.
See :gh:`124520` for discussion and links to changes in some affected
projects.


dbm
---

Expand Down