Issue 543098: start docs for PyEval_* functions (original) (raw)

Issue543098

➜

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.

classification

Title:	start docs for PyEval_* functions
Type:	Stage:
Components:	Documentation	Versions:

process

Created on 2002-04-12 17:08 by theller, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Files
File name	Uploaded	Description	Edit
ceval.tex	theller,2002-04-12 17:08	Prototypes marked up in LaTeX

Messages (4)
msg39551 - (view)	Author: Thomas Heller (theller) *	Date: 2002-04-12 17:08
The start of a new (sub)section for the api manual. Should this go into api/utilities?
msg39552 - (view)	Author: Thomas Heller (theller) *	Date: 2002-04-12 17:21
Logged In: YES user_id=11105 Typo in the summary.
msg39553 - (view)	Author: Fred Drake (fdrake)	Date: 2002-04-12 19:26
Logged In: YES user_id=3066 The section needs a better heading. ;) (The Utilities chapter is fine; it can go at the end.) I'd also like to see more content in the section before it gets added (though that's just as easily fixed once the boilerplate is checked in). It would be good to review the material in "Documenting Python"; this is part of the standard documentation. PyEval_SetProfile() and PyEval_SetTrace() are already documented. Please continue with this!
msg39554 - (view)	Author: Thomas Heller (theller) *	Date: 2002-04-12 19:32
Logged In: YES user_id=11105 > The section needs a better heading. ;) This is where I need your help. These functions are in ceval.c, and I even don't know why. The reason would probably make a good header. Suggestions? Since I currently have no internet access except email and http, I will work on a local version. I'm also relying on you checking and fixing the markup ;-)