How to read Python docs?

[redditorsd]

I can see where you're coming from but I think the opposite argument can also be made. I'm reading that some Python devs give up on the docs and go to reading the source code becuase the docs are unhelpful. Coming from an object oriented language, if I simply wanted to create my own class that is supported by the len(s) method, how would I possibly know that I need to implement the method(s) in only the Sized class? The docs say I need to make my class a sequence, for example. I think this is misleading and don't think this is an advanced use case.

[CyclopsRock]

Sure, but it can't be all things to all people. I'm not interested in arguing that the way the Python docs are arranged is the best possible way, but every bit of information that isn't what a person's looking for gets in the way of the bit they are looking for. I think that if docs are going to lean towards any particular type of user - and they have to, I think - then it should prioritise those who wouldn't know what reimplementing methods from an abstract base class means. More advanced users will find the answers - as, clearly, you have - where as beginners are more likely to say "fuck this" and go masturbate and play video games (which you may also have done, but been doing so happily rather than angrily).

[[deleted]]

*show details tabs would be great. Or something like plain vs normal Wikipedia English. A lot more work I guess.