This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients ncoghlan
Date 2008-11-21.23:43:56
SpamBayes Score 9.20884e-06
Marked as misclassified No
Message-id <1227311037.4.0.355018022535.issue4385@psf.upfronthosting.co.za>
In-reply-to
Content
The memory layout of PyType object's changes in Py3k from the
*compiler's* point of view. This means PyObject_HEAD_INIT can no longer
be used to initialise PyVarObject type definitions.

However, the documentation doesn't point this out (or document
PyVarObject_HEAD_INIT at all), and the compiler warnings currently
generated are not clear. Suggestion is to remove PyObject_HEAD_INIT from
Py3k entirely so this becomes a compile error instead of a warning, and
then better document the situation so extension authors know how to
correctly initialise the affected C structs.

See mailing list thread at:
http://mail.python.org/pipermail/python-3000/2008-November/015241.html
History
Date User Action Args
2008-11-21 23:44:02ncoghlansetrecipients: + ncoghlan
2008-11-21 23:43:57ncoghlansetmessageid: <1227311037.4.0.355018022535.issue4385@psf.upfronthosting.co.za>
2008-11-21 23:43:56ncoghlanlinkissue4385 messages
2008-11-21 23:43:56ncoghlancreate