How Python Compares Floats and Ints: Why It Can Give Surprising Results
blog.codingconfessions.comAnother Python gotcha and an investigation into its internals to understand why this happens
You must log in or register to comment.
!technology@lemmy.worldYou are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@lemmy.world
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
- 1 user online
- 220 users / day
- 609 users / week
- 1.39K users / month
- 4.49K users / 6 months
- 1 subscriber
- 7.41K Posts
- 84.7K Comments
- Modlog
- mods:
Did nobody read the manual?
IEEE 754 double precision: The 53-bit significand precision gives from 15 to 17 significant decimal digits precision.
If i’m comparing ints with floats, it is my fault in the first place
Exactly, I’d expect a warning, if not an error.