Does anyone remember an old blog post where someone used various Python language hacks to override boolean primitives, such that the statement false == true evaluated as true? I’m 90% sure it was python, but maybe it was some other language.
I’ve been looking for that post recently, but haven’t had any luck.
Thanks to antagonistic for finding it! I guess it was less of an “exploit”, and more of a “please don’t touch the loaded foot-gun”
Yes! Thanks
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?They are constants, like None, which has always been around.
all builtin constants are capitalised.
All… five of them!
The other 7 are all lowercase. (One of you ignore site)
yeah but dunders usually aren’t included in counts
I feel like you hear fuckery like that more in JavaScript.
Maybe they did “False is True” because they’re both the same Python object?
I just checked and they aren’t.
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.
I really need to stop trusting how durable this language is.
Python doesn’t have
trueorfalsekeywords, nor any other primitives by those names.So either you’re thinking of a different language, or different identifiers, or someone assigned equal values to variables with those names and then blogged about it.
This changed in 3.0 to my knowledge. Ref: https://wiki.python.org/moin/Python3.0#f
That change is about
TrueandFalse, nottrueandfalse. If OP was thinking of the former pair, it would seem my “different identifiers” guess was correct.
