Python(and most modules and frameworks) and C++ for the best documentation for sure

In what world

@12bitfloat do you not agree? Python's docs are awesome
C++ docs may seem cryptic but they are full

@alert Pyhton has some of the worst docs I've ever had to deal with. Mostly because it's dynamically (and more or less weakly) typed so you have no idea what's happening anywhere unless the documentation explicitely tells you which it never does

The last experience with Python was with the PlatformIO scripting API (https://docs.platformio.org/en/... )

What about a comprehensive list of built-in targets? How can you even invoke custom targets? When does your build script run in context of the build phase? No idea and docs don't tell you.
Turns out it's maybe losely based on SCons (no mention of a version number though)

Except `AddCustomTarget` doesn't appear to exist in SCons so I still have no idea how it actually works. My tests didn't yield anything

In the end I just copied some other script off GitHub and changed it to do what I need. It's an ugly hack and not at all how you should do it but at least it sorta works

@12bitfloat it may because the library is bad itself
I see a lot of typed module these days
Also most used tools and frameworks, like django (and other open source apps), flask, fastapi are pretty well documented

@12bitfloat may be it's just web part of python
I'm not really into data science

@alert The major libraries are probably documented much, much better. But I think the problem is more systemic since Python at it's core is still a "hack it until you make it" environment. And the same disadvantages this model has for writing robust programs it also has for comprehending code. Because documentation isn't just about the written, deliberate docs. It's also about the code documenting itself which is where I believe the core problem of a dynamic scripting language lies