I dislike treating None as an equivalent for the empy list, but that does not further the discussion…

I hurt myself in confusion while reading the second quote. Is it the right quote? (also, nazi (relating to the nsdap) is probably not the right word, did you mean fascist?)

I agree. So if None is a valid input we should check it first, and then check if the length is zero. In this situation, we see a type error only if the programmer screwed up and everything is explicit

I don’t really understand the point about exceptions. Yeah “not foo” cannot throw an exception. But the program should crash if an invalid input is provided. If the function expects an optional[list] it should be provided with either a list or None, nothing else.

Passing None to a function expecting a list is the error…

Well, in your case it is not clear whether you intended to branch in the variable foo being None, or on the list being empty which is semantically very different…

Thats why it’s better to explicitly express whether you want an empty collection (len = 0) or a None value.

I really dislike using boolean operators on anything that is not a boolean. I recently made an esception to my rule and got punished… Yeah it is skill issue on my part that I tried to check that a variable equal to 0 was not None using “if variable…”. But many programming rules are there to avoid bugs caused by this kind of inattention.

Des chocolaitines?

Please tarrif those american trucks! please please please!

Swiss plugs are the best. I won’t be neutral on this !

Ok I wanted to confirm ^^ I’m not crazy it really is girl stink

What is girl stink?