Interesting. Since i'm not a Python expert, i'd like to look at these. But the doc gives ample gratis links to Open Source this or that or author know-how exhibition links to remote book i don't really care about, but here there's no link.
Does not focus on the task users need to do. Instead, the doc is oriented towards tech geeking.
Does not inform the reader at the right places where a new function is replacing the old.
Does not provide relevant cross-links. (while provding many irrelevant links because of Open Source or Tech Geeking fanaticism)
Add cross-links to relevant modules.
Mention and add link at the right place supplanted functions.
Orient the doc to tasks and manifested functionalities. Think like functional programing: input and output specification, and document them. This will help focus and precision in the doc. Avoid prose-like descriptions. Avoid drilling on remotely related tech/unix/C esoterica. ⁖ Do not mention as a documentation how they are implemented. Mention implementation if the programer must know it in order to use it properly, and as side note. This way, the language becomes focused as a independent tool (⁖ Mathematica, Java, Scheme, emacs) (which may provide ample capabilities to interface/connect to other technologies), instead of heavily intermixed and dependent with a bunch of other things (unix things: Perl, Apache, shells).