this post was submitted on 27 May 2024
134 points (94.1% liked)

Technology

59428 readers
2824 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
134
How Python Compares Floats and Ints: When Equals Isn’t Really Equal (blog.codingconfessions.com)
submitted 5 months ago by abhi9u@lemmy.world to c/technology@lemmy.world
43 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] kakes@sh.itjust.works 18 points 5 months ago* (last edited 5 months ago) (1 children)

I assume this is because that number is so large that it loses precision, in which case this is more of a quirk of floating point than a quirk of Python.

Disclaimer: Have not read the article yet.

[–] magic_lobster_party@kbin.run 16 points 5 months ago

It’s both. As you said it’s because of loss of floating point precision, but it’s also with some of the quirks how Python compares int with float. These two together causes this strange behavior.