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 serhiy.storchaka
Recipients eric.snow, giampaolo.rodola, rhettinger, serhiy.storchaka, terry.reedy
Date 2012-12-16.12:08:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355660066.4033.28.camel@raxxla>
In-reply-to <1355603556.09.0.994575691774.issue16669@psf.upfronthosting.co.za>
Content
> 1. Most data attributes cannot have individual docstrings, so I expect the class docstring to list and possibly explain the data attributes. 

But almost all PyStructSequence field have individual docstrings.

> This does not create a second new class and is not a 'trick'.

Thanks for the tip.

> I presume that is why property docstrings are not used much.

Indeed, only 84 of 336 Python implemented properties have docstrings .
However this is even larger percent than for methods (about 8K of 43K).
And 100 of 115 PyStructSequence field have docstrings.

I think Python should have more docstrings, not less.
History
Date User Action Args
2012-12-16 12:08:03serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, terry.reedy, giampaolo.rodola, eric.snow
2012-12-16 12:08:03serhiy.storchakalinkissue16669 messages
2012-12-16 12:08:03serhiy.storchakacreate