Python.. I seriously thought we understood each other but I guess it's all over now.💔

About to hit repost when it struck me.

I see nothing wrong here

@Kimmax Why is it False in the second case and not in the first

I wonder if 0 is an object.

@ishank-dev https://stackoverflow.com/questions...

This link from the other link explains the integer thing:

https://stackoverflow.com/questions...

@halfflat People who program C++ shouldn't throw stones:

int array[10];

0[array] = 5;

;-)

I know, I don't remember the last time I used a legit array in C++, but meh.

@Demolishun Actually explains the same thing, but yours is more comprehensive :)

@Kimmax In the second question it explains that -5 to 256 are indeed objects when assigned to a variable. Not sure what happens when math is applied though.

Identity a != Value 1000
Identity a = identity implicit(0) = boolean

Algorithm at it aga...wait...

Wait why did you post this twice with a different caption?

@AlgoRythm because both are different

I never even thought about trying to use the "is" operator with numbers. I also will never become a pentester.

In python (and many other languages including java)

Often used values are pooled. For example numbers up to 256 are pooled in python.

That means that all numbers up to 256 will have a single place in memory

a = 256
a is 256 results in True

But a = 257
a is 257 will be False

The idea is to save time and space for values that appear commonly in code

This is normal behaviour and also why you should be using == instead of reference comparison (is)