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 rhettinger
Recipients Jay.Parlar, daniel.urban, davide.rizzo, docs@python, eric.araujo, ezio.melotti, franck, martin.panter, nedbat, rhettinger
Date 2019-08-29.06:07:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> - use the same names for __get__ arguments throughout 
> the documentation (both the reference and the tutorial),
>  e.g. __get__(self, instance, owner)

Early on the choice of variable names diverged (including in various PEPs and in the C source).  I will harmonize where I can but the cat is out of the bag.

> - decide whether the third argument should be optional, 
> or state the common usage in the reference, and fix 
> accordingly the examples in the howto

PEP 252 specifies that it is optional.  Various builtin descriptors also make it optional (function_get, staticmethod_get, classmethod_get, and property_get).

I'm fixing the main docs and non-compliant code in PR 12992

> explain data, non-data and read-only descriptors in 
> the __set__ reference, or more simply, how the >
> defintion of __set__ affects these things.

That is reasonable.  Will add to the datamodel docs.

[Jay Parlar]
> Another problem is that the examples and text in 
> the section "Functions and Methods" is no longer 
> correct in 3.x. Namely the the references to
> unbound methods

That was fixed a good while ago.
Date User Action Args
2019-08-29 06:07:51rhettingersetrecipients: + rhettinger, nedbat, ezio.melotti, eric.araujo, daniel.urban, docs@python, davide.rizzo, Jay.Parlar, martin.panter, franck
2019-08-29 06:07:50rhettingersetmessageid: <>
2019-08-29 06:07:50rhettingerlinkissue12077 messages
2019-08-29 06:07:50rhettingercreate