[Python-Dev] Issue10403 - using 'attributes' instead of members in documentation

Tres Seaver tseaver at palladion.com
Tue Jun 28 14:43:35 CEST 2011


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

On 06/28/2011 06:44 AM, Fred Drake wrote:
> On Tue, Jun 28, 2011 at 2:33 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> The two terms I've got out of this thread are "callable attributes"
>> (instance/static/class methods, etc) and "data attributes" (everything
>> else). Both seem reasonable to me, creating two largely disjoint sets
>> that together cover all the different kinds of attribute you're likely
>> to encounter.
> 
> But "callable attributes" aren't the same thing as methods; most are methods,
> but not all.  Sometimes, they're data used by the object.  The fact that
> data attributes can be callable is irrelevant.

Isn't it fuzzy / incorrect to refer to any callable attribute as a
method until it have been extracted via the dot operator / getattr, and
therefore bound via descriptor semantics?  In this sense, 'staticmethod'
doesn't create a "method" at all -- it just defeats the default creation
of a method-yielding descriptor.


Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4JzHcACgkQ+gerLs4ltQ6I5ACZAXlBsZkrzQowKYBmJE4NQb4V
F14AnRtkWByqwpRATan4OOTMgPqwyjxH
=hru9
-----END PGP SIGNATURE-----



More information about the Python-Dev mailing list