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.

Author eli.bendersky
Recipients docs@python, eli.bendersky, eric.araujo, eric.snow, python-dev, terry.reedy
Date 2011-08-16.02:45:05
SpamBayes Score 2.024573e-08
Marked as misclassified No
Message-id <1313462706.63.0.108833753683.issue12672@psf.upfronthosting.co.za>
In-reply-to
Content
Terry, I'm not 100% sure about what you mean by "Python wrapper objects ... visible from Python", but I think I'll disagree.

There's a big difference between "C functions" in general and "type methods" this document speaks of. Let's leave list aside for a moment, since its being built-in complicates matters a bit, and let's talk about the "Noddy" type this documentation page plays with.

You may implement "normal" methods for Noddy, such as the "name" method added in the first example, by defining an array of PyMethodDef structures and assigning it to tp_methods.

On the other hand, the other tp_ fields imlpement special type methods (used by __new__, __str__, getattr/setattr, and so on). This is the major difference. Both are C functions, but some implement special type methods and some implement "normal" object methods.

If this is also what you meant, I apologize for disagreeing :-)

I believe my latest rephrasing proposal is reflecting the above understanding.

P.S. as for s/that/than/ further down - good catch, will add it to the patch when we decide about the first issue
History
Date User Action Args
2011-08-16 02:45:06eli.benderskysetrecipients: + eli.bendersky, terry.reedy, eric.araujo, docs@python, python-dev, eric.snow
2011-08-16 02:45:06eli.benderskysetmessageid: <1313462706.63.0.108833753683.issue12672@psf.upfronthosting.co.za>
2011-08-16 02:45:06eli.benderskylinkissue12672 messages
2011-08-16 02:45:05eli.benderskycreate