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 r.david.murray
Recipients anthony-flury, docs@python, mark.dickinson, r.david.murray, steven.daprano
Date 2016-08-31.00:39:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472603972.1.0.749177056808.issue27901@psf.upfronthosting.co.za>
In-reply-to
Content
The docs do not so much assume you know what the library does, as they assume you know how python3 works.  Which is to say, that bound methods are obtained from instances and that functions defined on a class are functions.  That's documented in the data model docs, and the inspect docs in general assume you understand the python data model and are using inspect to probe it.

As Steven said, if you can point specifically to something you think can be improved we will consider it, but know that the python3 docs are in general written without respect to how python2 worked.  There are very few references to python2 in the python3 docs, and this is by design.  The story is different in the python2 docs, so conceivably there could be something inserted there about the python3 difference.
History
Date User Action Args
2016-08-31 00:39:32r.david.murraysetrecipients: + r.david.murray, mark.dickinson, steven.daprano, docs@python, anthony-flury
2016-08-31 00:39:32r.david.murraysetmessageid: <1472603972.1.0.749177056808.issue27901@psf.upfronthosting.co.za>
2016-08-31 00:39:32r.david.murraylinkissue27901 messages
2016-08-31 00:39:31r.david.murraycreate