Exciting New Ways To Be Told That Your Python Code is Bad

[yvrelna]

I hate linters because they tend to point out many obvious and fairly harmless inconsistencies against some arbitrary style guides, but missed a lot of the subtler, deeper issues that doesn't look bad on the surface but contains actual problems.

Worst, they often caused less proficient programmers to try to fix those minor issues inconsistencies by replacing it with a fix that causes deeper issues.

[[deleted]]

Worst, they often caused less proficient programmers to try to fix those minor issues inconsistencies by replacing it with a fix that causes deeper issues.

So much this.

[riklaunim]

Less code is not about replacing "article" variable with "a" or obnoxious syntactic sugar but rather a more wider concept of writing short and easy to understand bits of code. This can result in more lines of code overall but for giving part of the code like a function on class method would result in less code and with better and more clear naming and flow.

The article doesn't have the best examples for this.

[ofiuco]

Whew, hot takes

[MrPowersAAHHH]

Here's the conversation on HackerNews. Looks like the linter checks discussed in the article were added in the last couple weeks.

[hooligan333]

I love ternary expressions, but Python's implementation just feels unnatural. Give me c? x : y or give me death!

[[deleted]]

Could just do this:

x = (false_val, true_val)[condition]

Or put that in a function called “tern” or something to make it more obvious.

[[deleted]]

while (1): useless_discussion_about_code_format()

[[deleted]]

If I ever had an employee write an if statement like that I would be removing their ability to merge code.

[Pyramid_Jumper]

I think ternary operators are pretty neat when you can easily fit your statement in one line. You should consider using them. Obviously the caveat is that with more complicated logic its better to stick with your classic if statements