The Python criticism I heard is that it makes it harder for library writers because they have to dive into source code. But here's the thing, when using a dynamic language with duck typing you don't really care what type specifically something is, only that you can iterate over it. I experienced the difference when porting someone's Python application to Rust. In Python, I didn't care what type the argument is, only what operations are performed. When writing the Rust equivalent, the Rust compiler was quick to complain it wanted to know the exact type.
So I think Python docs are good for dynamic languages, while Rust documentation pleases people used to static languages.
So I think Python docs are good for dynamic languages, while Rust documentation pleases people used to static languages.