Isn't it more akin in this case to worrying about too much carbon dioxide in the air?

Why is it akin to that? Doesn't the salt come from the sea in the first place?

A more apt comparison than you realize.

Most of the carbon we spew into the atmosphere came from the air. Ancient plants took it in via respiration.

That still doesn't make it a good comparison. The salt emitted by desalination plants is already in the sea now, it's not salt that went somewhere else.

And the water we take out eventually goes back.

cf. would invite a fair bit of confusion on an article about cloudflare

I agree! That's why I think it's probably just a confusion between entities. It doesn't make sense either as example or as a comparison (although IMO it makes more sense as the latter).

(For the OP: I'm sorry if I misinterpreted you.)

It's all good. Hardly matters. It was just becoming too big a discussion for something far too minor. Any frustration I had from being misunderstood (primarily self-directed) was alleviated from satvikpendem guessing correctly what I intended.

Curious which of these are not covered by ruff

Almost all of them are covered by just having some experience in the language and a minimum of good taste; and many are covered by Python itself.

Also, a bunch of things are being bundled together as "anti-patterns" here that just don't match the traditional idea of what I always saw written up that way. A lot of it is just "failure to use the usual pattern".

And a lot of the rationale is very weak tea.

For example, don't assign a lambda to an identifier, because a function will show up in a stack trace. But it's OK to use the lambda directly. (huh. What happened to the necessity for the stack trace?)

(FWIW, I think that in some cases assigning lambdas to identifiers is peachy-keen fine. Visually, I immediately know I'm looking at something that doesn't itself produce any side-effects.)

"Using single letter variable names." Uh, yeah, when to do this isn't Python-specific, and includes some cases when it's actually better.

"Not using defaultdict()" Sure, sure, having keys automagically populate is goodness. But then, "Dynamically creating variable/method/function names" is an anti-pattern. Schizophrenic much?

And then, we have the outright lies, such as:

"When a method is not preceded by the @staticmethod or @classmethod decorators and does not contain any references to the class or instance (via keywords like cls or self), Python raises the Method could be a function error. This is not a critical error, but you should check the code in question in order to determine if this section of code really needs to be defined as a method of this class."

Nobody should take advice from a third-grader who can't discern the difference between the interpreter and his preferred lint-like substance.

Possibly Audacity, given the direction v4 is taking. Great video essay / update here: https://youtu.be/QYM3TWf_G38

A lot of theorising above, but this seems like the earliest reference

This feels like a somewhat closed minded approach given both tools are in their infancy

Pyright is incredibly slow in my experience, I've seen it take over a minute on complex codebases

See also https://github.com/atopile/atopile

I guess we can say both instances are electromagnetically attached. But then, basically everything is.

It's (7F) ELF

Hmm, I would expect that to be 31F, if it stood for "ELF" in correct Hexspeak.