[macspoofing]

>2. The async nature of the library is unpleasant. Can never be sure when/where your code will run.

>3. Lots of 'magic' Python variables and methods that you have to override, but there's no way to discover them in your IDE through the type system ...

>5. It seems to leak memory.

Welcome to Python. =)

[coldtea]

None of those are real Python problems...

[FridgeSeal]

An over-abundance of “magic” in Python libraries and tools is definitely a real Python problem.

[coldtea]

"Magic" is a superstitious programming term.

Python libs can and do use dunder method overrides, operator overloading, and so on. If it was common to rewrite the AST, or have other action-at-a-distance, I'd give this some credit, but those are still century old PL features, and well specified mechanisms, not something one can't reason about.

Python I find to be (and I'd say most find it to be, hence its popularity on fields like Physics and such, even by non-programmers by trade) one of the easiest languages to read programs in and understand their intent.

Which exacly library, say of the 100 most commonly used ones on Pypi to keep this focused, is particularly problematic?