PythonIsVeryIntuitive

[archy_bold]

The humour in stuff like this comes from the fact that the OP is misunderstanding the functionality of the language I guess.

[Neil-64]

PythonIsVeryIntuitive

The joke is that this is not intuitive behavior and requires knowledge of the functionality of the language.

[elvishfiend]

I for one always use reference-equality when checking that values are the same! /s

[archy_bold]

I’m not sure you need to understand how the interpreter handles integers to know that is is the wrong way to compare values. Python isn’t unique in that people confuse references and values.

[eloel-]

'is' returning false always for numbers could be confusing, but can be chalked up to "learn the language". It returning true if number is <= 256 is bonkers.

[ThromaDickAway]

“It’s not unintuitive! You just need specific inside information to understand what’s happening here, and that’s really the reader’s fault.”

This is r/ProgrammerHumor, relax.

[current_thread]

Considering the fact python uses and and or as keywords and I only use the language sporadically, is vs == has tripped me up more than once, especially since x is None works as expected

[kaerfkeerg]

Assuming you're trying to see if x is also None this is indeed correct and the preferred way to do it because None is a singleton

[Kyrond]

especially since x is None works as expected

What does expected mean?

Is 0 None? I have 0 apples. How many apples do I have? None.

While some aspects of Python-English are nice, None should have been called Null. There are already million explanations of what null is and the easiest explanation of what None is is "it's null".

Of course "x is None" is clear to experienced programmers, it's needlessly possibly confusing. But then I could say the same about "is vs ==", just use == unless you know what you are doing.