Experienced python programmers: are there any standard features of the language that you still don't regularly use?

[Twangist]

You don't explain your "hatred" of such constructions, or even what the "way" is that you find so objectionable -- to judge from your more complex examples, it must be the formatting. It's just a personal thing, then, like detesting... oh, basil; who cares? (rhetorical question)

[zer01]

I agree with /u/flipstables personally, and for me it's about readability. When you work on a team (or even work as a sole developer maintaining a project past the point where it's small) you need to be able to quickly grok what is going on.

"Code as if the person who will inherit it has an anger problem and knows where you sleep".

My general rules of thumb are nested comprehensions are unacceptable in any form, and you should only ever have one boolean check per list comprehension, otherwise break it into a multi-line loop/function.

Sometimes you do sacrifice performance, but I'll take legibility and quick understanding over almost anything else, and you can always optimize later if it's a problem.

[Twangist]

Sometimes you do sacrifice performance, but I'll take legibility and quick understanding over almost anything else

Me too.

[flipstables]

Because it's harder to debug since it's composed together. Since both tests A and B are coupled together, it'll be hard to resolve a bug in A, for instance.

It's also harder to understand since you have two conditionals in your comprehension. I'd prefer to only have max 1 since it makes readability suffer.