[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered
Éric Araujo mer...@netwok.org added the comment: Thanks for the investigation! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9728 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered
Éric Araujo mer...@netwok.org added the comment: I tried to find the old FAQ in the Debian package for 2.5 but failed. It looks like this require a fair bit of version control exploration. -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9728 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered
Terry J. Reedy tjre...@udel.edu added the comment: As I remember, the FAQ was once that, *the* (giant) FAQ, with numbered sections. When broken into pieces, the order may have been re-arranged. Given that the broken reference is in extending/windows, I would look in both the Extending and Windows FAQs. However, I found neither 'PyType_Type' nor 'PyVarObject_HEAD_INIT' nor 'initialization' in either. Besides removing the dead reference, you could either look through the revision history of the file or ask on pydev if you need the info. The split-up FAQs first appear in a release doc set in Python 2.6.4, documentation released on 25 October 2009. I do not know if the earlier, unitary FAQ is in the repository or not. -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9728 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered
New submission from Daniel Stutzbach dan...@stutzbachenterprises.com: 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. -- assignee: d...@python components: Documentation messages: 115285 nosy: brian.curtin, d...@python, stutzbach, tim.golden priority: normal severity: normal stage: needs patch status: open title: Docs point to FAQ Section 3, but FAQs are not numbered ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9728 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
