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 josh.r
Recipients, docs@python, gvanrossum, josh.r, rhettinger
Date 2020-12-09.22:41:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If this is going to be closed as rejected, I think it still needs some improvement to the documentation. Right now, the docs for abstractproperty (deprecated in favor of combining property and abstractmethod) state:

"If only some components are abstract, only those components need to be updated to create a concrete property in a subclass:"

This heavily implies that if *all* components of the property are abstract, they must *all* be updated to create a concrete property on the subclass, when that is not the case (it's documenting a special way of overriding just one component by borrowing the base class, not a normal means of defining a property). If nothing else, mentioning this quirk in the docs seems like it would save confusion (e.g. ).
Date User Action Args
2020-12-09 22:41:44josh.rsetrecipients: + josh.r, gvanrossum, rhettinger, docs@python,
2020-12-09 22:41:44josh.rsetmessageid: <>
2020-12-09 22:41:44josh.rlinkissue39707 messages
2020-12-09 22:41:44josh.rcreate