[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

Éric Araujo added the comment: Thanks for the investigation! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

Daniel Stutzbach added the comment: Fixed in r84810, r84811, and 84812. For anyone curious, the old FAQ entry is here: http://web.archive.org/web/20010203161100/http://www.python.org/doc/FAQ.html#3.24 -- resolution: -> accepted stage: needs patch -> committed/rejected status: open ->

[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

Daniel Stutzbach added the comment: Nevermind... archive.org has it. :-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

Daniel Stutzbach added the comment: It looks like the FAQ used be generated using Tools/faqwiz/faqwiz.py (which no longer exists). According to that file: --- This is a CGI program that maintains a user-editable FAQ. It uses

[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

Daniel Stutzbach added the comment: Where does/did the FAQ live in the version control tree? -- ___ Python tracker ___ ___ Python-bugs

[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

Éric Araujo 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

[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

Terry J. Reedy 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. Howeve

[issue9728] Docs point to FAQ Section 3, but FAQs are not numbered

New submission from Daniel Stutzbach : 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