this post was submitted on 15 Aug 2025
32 points (97.1% liked)

Programmer Humor

27196 readers
1419 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
anzo@programming.dev
Feyter@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
32
Blog post where someone used Python quirks to evaluate false == true (lemmy.dbzer0.com)
submitted 2 months ago* (last edited 2 months ago) by CrackedLinuxISO@lemmy.dbzer0.com to c/programmer_humor@programming.dev
8 comments fedilink hide all child comments
 

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"

top 8 comments
sorted by: hot top controversial new old
[–] Antagnostic@lemmy.world 21 points 2 months ago (1 children)

This?

[–] CrackedLinuxISO@lemmy.dbzer0.com 7 points 2 months ago

Yes! Thanks

[–] ExperimentalGuy@programming.dev 8 points 2 months ago (1 children)

I feel like you hear fuckery like that more in JavaScript.

[–] who@feddit.org 4 points 2 months ago* (last edited 2 months ago) (1 children)

Python doesn't have true or false keywords, 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.

[–] Antagnostic@lemmy.world 4 points 2 months ago (1 children)

This changed in 3.0 to my knowledge. Ref: https://wiki.python.org/moin/Python3.0#f

[–] who@feddit.org 4 points 2 months ago* (last edited 2 months ago)

That change is about True and False, not true and false. If OP was thinking of the former pair, it would seem my "different identifiers" guess was correct.

[–] LodeMike@lemmy.today 3 points 2 months ago

Maybe they did "False is True" because they're both the same Python object?