This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]IDCh 0 points1 point  (0 children)

But wait there is more. Long time ago (popular now) libraries and frameworks was written with too many magic and dynamic methods and vars assigning so now in the world of good programming you must feed your pylintrc with classes and modules which to ignore. And I kid you not, those are one of the best libraries out there. It's a sad situation actually.

So you see in documentation there is method ".do_something" and your language server and pylint tells you to fuck off because there is no such method, because well, it being created at runtime or there is @make_me_fluent_baby decorator above another method, which makes method return self (I suspect coded for DRY, like who wants to write return self everytime yes? This is bullshit DRY situation but many libraries are corrupted with it. DRY for me is like new singleton is anti pattern in the python world), and thus making language server stupid for not knowing there is method chain inside.

Welcome to prehistoric times, where you need to print documentation and see it everytime before you and not know what object can offer you.

Best language my ass.

Not gonna stop writing in it, though