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, pitrou, python-dev
Date 2011-08-12.08:43:42
SpamBayes Score 0.00092878524
Marked as misclassified No
Message-id <1313138623.38.0.455349240903.issue12672@psf.upfronthosting.co.za>
In-reply-to
Content
> Would it be clearer if we replaced the literal with a name?
>
>  These C functions are called “type methods” to distinguish them from
> - things like [].append (which we call “object methods”).
> + methods bound to specific instances (things like sys.path.append),
> + which we call “object methods”.

No, I don't think this is the intention (bound vs. unbound). I think the distinction is between special methods recognized by Python, and "plain object methods" defined by the user. Not sure how to express this clearly in the docs though.

Re PEP-7 cleanup: done some for extending/newtypes.html - not sure everything is fixed but it's a bit better now.
History
Date User Action Args
2011-08-12 08:43:43eli.benderskysetrecipients: + eli.bendersky, pitrou, eric.araujo, docs@python, python-dev
2011-08-12 08:43:43eli.benderskysetmessageid: <1313138623.38.0.455349240903.issue12672@psf.upfronthosting.co.za>
2011-08-12 08:43:42eli.benderskylinkissue12672 messages
2011-08-12 08:43:42eli.benderskycreate