➜
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.
Created on 2007-07-23 05:35 by lpd, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg32541 - (view) | Author: L. Peter Deutsch (lpd) | Date: 2007-07-23 05:35 | |
Doc section 3.4.2.3 says: Data descriptors define both __get__() and __set__(). Non-data descriptors have just the __get__() method. This is not quite detailed enough. By experiment, the next paragraph is the whole story, which I think should replace the above two sentences. A descriptor can define any combination of __get__(), __set__(), and __delete__(). If it does not define __get__(), then accessing the attribute (a.x) will return the descriptor itself. If the descriptor defines __set__() and/or __delete__(), it is a data descriptor; if it defines neither, it is a non-data descriptor. I realize that some combinations of __get__(), __set__(), and __delete__() are not very useful, but the documentation should cover all the cases. |
|||
| msg55225 - (view) | Author: Georg Brandl (georg.brandl) *  |
Date: 2007-08-23 21:43 | |
Added a footnote in rev. 57355. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:25 | admin | set | github: 45235 |
| 2007-08-23 21:43:03 | georg.brandl | set | status: open -> closed resolution: fixed messages: + msg55225 nosy: + georg.brandl |
| 2007-07-23 05:35:32 | lpd | create | |