[issue18353] PyUnicode_WRITE_CHAR macro definition missing
New submission from Wolf Ihlenfeldt: Above macro is mentioned in the documentation (3.3.2), but does not appear in the header files. Associated function PyUnicode_WriteChar() is present and works as expected. -- assignee: docs@python components: Documentation, Unicode messages: 192247 nosy: Wolf.Ihlenfeldt, docs@python, ezio.melotti priority: normal severity: normal status: open title: PyUnicode_WRITE_CHAR macro definition missing type: compile error versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue18353> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18494] PyType_GenericSet/GetDict functions misnamed in docs?
New submission from Wolf Ihlenfeldt: Are the names of functions PyType_GenericSetDict and -GetDict correctly documented (for 3.3.2), or should they be documented as PyObject_GenericGet/SetDict instead? The PyType-prefixed names are out of place in the section, and functions of these names not in the source. The PyObject_-variants are present. -- assignee: docs@python components: Documentation messages: 193315 nosy: Wolf.Ihlenfeldt, docs@python priority: normal severity: normal status: open title: PyType_GenericSet/GetDict functions misnamed in docs? versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue18494> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20066] PyStructSequence_NewType() not setting proper heap allocation flag?
New submission from Wolf Ihlenfeldt: If I am not mistaken, I think that PyStructSequence_NewType() should set the Py_TPFLAGS_HEAPTYPE flag in tp->flags (which it currently does not). The original version initially works fine, but ultimately crashes at exit time in finalization with Fatal Python error: type_traverse() called for non-heap type 'E_FILE' #0 0x712913d5 in raise () from /lib64/libc.so.6 #1 0x71292858 in abort () from /lib64/libc.so.6 #2 0x72360484 in Py_FatalError (msg=) at Python/pythonrun.c:2364 #3 0x722e5354 in type_traverse (type=0x10b47a0, visit=0x72374350 , arg=0x0) at Objects/typeobject.c:2892 #4 0x72374bd1 in subtract_refs (containers=0x726466c0) at Modules/gcmodule.c:386 #5 collect (n_uncollectable=, n_collected=, generation=2) at Modules/gcmodule.c:891 #6 collect_with_callback (generation=2) at Modules/gcmodule.c:1048 #7 0x72375436 in PyGC_Collect () at Modules/gcmodule.c:1476 #8 0x7235f698 in Py_Finalize () at Python/pythonrun.c:521 #9 0x76e70b70 in CSpythonFinalize () at nmds_python.c:44652 #10 0x00407399 in main () Setting the flag manually after creation lets the problem disappear. -- messages: 206923 nosy: Wolf.Ihlenfeldt priority: normal severity: normal status: open title: PyStructSequence_NewType() not setting proper heap allocation flag? type: crash versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue20066> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
