Work on the C API Reference

Christopher A. Craig com-nospam at ccraig.org
Wed Jul 4 23:07:48 CEST 2001


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm thinking about doing some work on Chapter 10 of the C API
reference so that there is better documentation of the various object
structures.  For instance rather than merely saying that
PyNumberMethods is a "Structure used to hold pointers to the functions
an extension type uses to implement the number protocol," I would
prefer that it laid out the structure of PyNumberMethods.  It would
also be nice if some common "gotchas" about methods were described (at
least stating something about coercion rules and the two methods of
coercion).

I would also like to include most (if not all) of the information in
"Extending and Embedding" in the reference manual so that there is one
central document describing everything about the API (so that you
don't, for instance, have to consult E&E for info on
PyArg_ParseTuple).

So before I start I want to ask: is this a worthwhile pursuit?  Is
there something I'm missing that makes this useless or undesirable?
Also how would I submit changes (especially realizing that I'm fairly
new to the API myself)?

Thanks,


- -- 
Christopher A. Craig <com-nospam at ccraig.org>
"Microprocessors cost $700 -- far too much for a tiny slice of refined,
 impurity-laced beach sand." Steve Gibson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt

iEYEARECAAYFAjtDhaQACgkQjVztv3T8pztEXwCbBv8Et73+vwj57d1mZl5vXmRk
9V8AoJEkCiORKLaFFr1ySrYEej+3RKe3
=RNl4
-----END PGP SIGNATURE-----



More information about the Python-list mailing list