Issue 1490989: Describe Py_DEBUG and friends... (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/43375

classification

process

Created on 2006-05-18 14:33 by skip.montanaro, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg50283 - (view)	Author: Skip Montanaro (skip.montanaro) *	Date: 2006-05-18 14:33
Here's a minimal first cut at describing Py_DEBUG and friends. Hopefully the description is detailed enough to be useful but not so detailed as to always be out-of-date. If nothing else, perhaps it will spur someone with better knowledge of these details to correct my mistakes and flesh out detail. As is usual for me, I have not run this through LaTeX. (I lack it at work.) It will need to be checked for correctness. Skip
msg50284 - (view)	Author: Michael Hudson (mwh)	Date: 2006-05-18 15:13
Logged In: YES user_id=6656 You know about Misc/SpecialBuilds.txt?
msg50285 - (view)	Author: Skip Montanaro (skip.montanaro) *	Date: 2006-05-18 15:48
Logged In: YES user_id=44345 If I did I forgot. I was grepping around trying to figure out what Py_DEBUG did exactly and saw the XXX comment in Doc/api/api.tex. I naively assumed at that point that Py_DEBUG and friends weren't documented. In any case, I think it makes sense to have some mention of the available options in api.tex, simply because it's the "official" documentation. It should reference Misc/SpecialBuilds.txt as well. Skip
msg50286 - (view)	Author: A.M. Kuchling (akuchling) *	Date: 2006-07-29 19:27
Logged In: YES user_id=11375 I've applied a slightly modified version of your patch in rev. 50948. Good work!