pybind/pybind11
Auf GitHub ansehen[BUG]: Python atexit broken with pybind11 version >= 2.9.2
Open
#4.459 geöffnet am 17. Jan. 2023
bughelp wanted
Repository-Metriken
- Stars
- (14.677 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 5T 2h) (10 gemergte PRs in 30 T)
Beschreibung
Required prerequisites
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
- Consider asking first in the Gitter chat room or in a Discussion.
What version (or hash if on master) of pybind11 are you using?
2.10.2
Problem description
We want to upgrade from pybind11 release 2.9.0 to 2.10.2, but we encountered an issue in the Python atexit (https://docs.python.org/3/library/atexit.html) functions, that our custom types are not registered anymore. With delta debugging we found that this PR caused the issue: https://github.com/pybind/pybind11/pull/3744
In my opinion the
detail::get_local_internals().registered_types_cpp.clear();
detail::get_local_internals().registered_exception_translators.clear();
calls should be after the Py_Finalize function call.
When I change the orders of those function calls, the problem is gone.
Reproducible example code
No response
Is this a regression? Put the last known working version here if it is.
2.9.1