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 stutzbach
Recipients brian.curtin, docs@python, stutzbach, tim.golden
Date 2010-09-01.01:49:05
SpamBayes Score 0.00054191693
Marked as misclassified No
Message-id <1283305749.34.0.483172641002.issue9728@psf.upfronthosting.co.za>
In-reply-to
Content
In Doc/extending/windows.rst, there's the following text:

------------------------------------------------------------------------
If your module creates a new type, you may have trouble with this line::

   PyVarObject_HEAD_INIT(&PyType_Type, 0)

Change it to::

   PyVarObject_HEAD_INIT(NULL, 0)

and add the following to the module initialization function::

   MyObject_Type.ob_type = &PyType_Type;

Refer to section 3 of the `Python FAQ <http://www.python.org/doc/faq>`_ for
details on why you must do this.
------------------------------------------------------------------------

If I assume that Section 3 means, the third link on the FAQ page, I can't find the FAQ that's being alluded to here.  There's a comment in Include/pyport.h that I believe to be related:

            /* Under Cygwin, auto-import functions to prevent compilation */
            /* failures similar to http://python.org/doc/FAQ.html#3.24 */

However, that link no longer goes to a particular question and I can't tell which question it once referred to.

I ran into this because I'm trying to understand the cause of the issue which I suspect is related to Issue #6672.
History
Date User Action Args
2010-09-01 01:49:09stutzbachsetrecipients: + stutzbach, tim.golden, brian.curtin, docs@python
2010-09-01 01:49:09stutzbachsetmessageid: <1283305749.34.0.483172641002.issue9728@psf.upfronthosting.co.za>
2010-09-01 01:49:07stutzbachlinkissue9728 messages
2010-09-01 01:49:05stutzbachcreate