Blog post where someone used Python quirks to evaluate false == true
-
I just checked and they aren't.
wrote last edited by [email protected]Maybe they defined them as variable names instead?
Or they could have just changed the language. Do you remember them compiling or editing C? (Python is usually run on cpython)
-
Maybe they defined them as variable names instead?
Or they could have just changed the language. Do you remember them compiling or editing C? (Python is usually run on cpython)
True is False gives false in Python 2.7.18 as well as 3.x. But, in 2.x, they aren't keywords, so you can say True=False=5 and then they are both the same object.
-
True is False gives false in Python 2.7.18 as well as 3.x. But, in 2.x, they aren't keywords, so you can say True=False=5 and then they are both the same object.
I really need to stop trusting how durable this language is.
-
I feel like you hear fuckery like that more in JavaScript.
-
The builtin names are True and False and they became keywords a while back. true and false are just ordinary variables that you can set to whatever you want.
Meanwhile, in Forth:
: 2 3 ; \ define 2 as 3 2 2 + . 6 ok \ shows that 2+2 is now 6God I hated that about Python. Why tf we capitalizing
TrueandFalse? -
God I hated that about Python. Why tf we capitalizing
TrueandFalse?all builtin constants are capitalised.
-
God I hated that about Python. Why tf we capitalizing
TrueandFalse?They are constants, like None, which has always been around.
-
all builtin constants are capitalised.
wrote last edited by [email protected]All… five of them!
The other 7 are all lowercase. (One of you ignore site)
-
All… five of them!
The other 7 are all lowercase. (One of you ignore site)
yeah but dunders usually aren't included in counts
-
all builtin constants are capitalised.
And they also don't follow the conventions for constants otherwise, which are all caps.
-
And they also don't follow the conventions for constants otherwise, which are all caps.
i think we're talking about different things.
