[issue39276] type() cause segmentation fault in callback function called from C extension

Change by Irit Katriel : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue39276] type() cause segmentation fault in callback function called from C extension

Giacomo Mazzamuto added the comment: Hello, the segmentation fault is also resolved by finalizing the initialization of InternalType by calling PyType_Ready(), just like you do with ExternalType -- nosy: +Giacomo Mazzamuto ___ Python tracker

[issue39276] type() cause segmentation fault in callback function called from C extension

Change by Pablo Galindo Salgado : -- Removed message: https://bugs.python.org/msg359687 ___ Python tracker ___ ___ Python-bugs-list

[issue39276] type() cause segmentation fault in callback function called from C extension

Pablo Galindo Salgado added the comment: static PyTypeObject InternalType should have PyVarObject_HEAD_INIT(_Type, 0) instead of PyVarObject_HEAD_INIT(NULL, 0) -- nosy: +pablogsal ___ Python tracker

[issue39276] type() cause segmentation fault in callback function called from C extension

New submission from Paweł Karczewski : How to reproduce: 1. Create callback function, which may take any object and run type() on it def builtin_type_in_callback(obj): type(obj) 2. Create C extension with two types defined in it - Internal and External. Eternal type should