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 eelizondo
Recipients benjamin.peterson, eelizondo, ronaldoussoren, twouters
Date 2018-08-29.15:41:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535557264.38.0.56676864532.issue34522@psf.upfronthosting.co.za>
In-reply-to
Content
@ronaldoussoren

* This change currently works for all CPython. If you are using this pattern then you probably want to be using PyType_FromSpec rather than having a static PyTypeObject as discussed in PEP384: https://www.python.org/dev/peps/pep-0384. In general, extensions should all be using PyType_FromSpec rather than static PyTypeObjects.

* As mentioned by Erik Bray in the e-mail thread, the usage of a static PyTypeObject with a PyVarObject_HEAD_INIT requires a compile-time constant. This causes problems cross-compatibility problems, especially with Windows. You can read more here: http://iguananaut.net/blog/programming/windows-data-import.html

In general, this pattern is just pervasive. It causes cross-compatibility issues, it can cause users to forget calling PyType_Ready on a type and we are better off without it.

Again, please read the mail thread. Everything that I'm saying here is all discussed there.
History
Date User Action Args
2018-08-29 15:41:04eelizondosetrecipients: + eelizondo, twouters, ronaldoussoren, benjamin.peterson
2018-08-29 15:41:04eelizondosetmessageid: <1535557264.38.0.56676864532.issue34522@psf.upfronthosting.co.za>
2018-08-29 15:41:04eelizondolinkissue34522 messages
2018-08-29 15:41:04eelizondocreate