At times simple arithmetic equations like 0.1+0.2 can give answers like 0.30000000000000004 instead of 0.3, in Python. Is Python broken then? No, this is not Python’s fault, it is the side effect of how floating numbers are represented in computers.<\/p>\n\n\n\n
You\u2019re doing basic math in Python, but the results don\u2019t make sense:<\/p>\n\n\n\n
print(0.1 + 0.2) # Expected: 0.3, Actual: 0.30000000000000004<\/code><\/pre>\n\n\n\nOr:<\/strong><\/p>\n\n\n\nprint(1.2 - 1.0) # Expected: 0.2, Actual: 0.19999999999999996<\/code><\/pre>\n\n\n\nIt seems like Python is doing something wrong, but it’s not just Python. This issue also occurs in most modern programming languages, including JavaScript, Java, and C.<\/p>\n\n\n\n
Why This Happens<\/h2>\n\n\n\n
Computers represent floating-point numbers in binary code. Most decimal fractions are difficult to be represented in a binary format. This results in small rounding errors.<\/p>\n\n\n\n
Example:<\/h4>\n\n\n\n\n- The number 0.1 can\u2019t be precisely represented in binary floating-point format.<\/li>\n\n\n\n
- So, 0.1 + 0.2 ends up being something like 0.30000000000000004.
<\/li>\n<\/ul>\n\n\n\nThis issue is part of the IEEE 754 standard used by almost all programming languages for floating-point representation. It\u2019s not a bug in Python, it’s just how computers work at the binary level.<\/p>\n\n\n\n
Steps to Resolve the Issue<\/h2>\n\n\n\nStep 1: Use round() for Display or Comparison<\/h3>\n\n\n\n
When displaying results or comparing float values, use round():<\/p>\n\n\n\n
result = 0.1 + 0.2\nprint(round(result, 2)) # 0.3<\/code><\/pre>\n\n\n\nStep 2: Use math.isclose() for Comparisons<\/h3>\n\n\n\n
Instead of doing:<\/strong><\/p>\n\n\n\nif result == 0.3:<\/code><\/pre>\n\n\n\nDo this:<\/strong><\/p>\n\n\n\nimport math\n\nif math.isclose(result, 0.3, rel_tol=1e-9):\n print(\"Close enough!\")<\/code><\/pre>\n\n\n\nThis is especially helpful in unit tests or financial applications where precision matters.<\/p>\n\n\n\n
Step 3: Use decimal.Decimal for High-Precision Arithmetic<\/h3>\n\n\n\n
Python\u2019s decimal module allows decimal arithmetic with better precision and control:<\/p>\n\n\n\n
from decimal import Decimal\n\na = Decimal('0.1')\nb = Decimal('0.2')\nprint(a + b) # 0.3<\/code><\/pre>\n\n\n\nThis is particularly useful for financial calculations where exact decimal representation is critical.<\/p>\n\n\n\n
Step 4: Use fractions.Fraction for Exact Rational Numbers<\/h3>\n\n\n\n
You can also use the fractions module when you want exact representations of fractions:<\/p>\n\n\n\n
from fractions import Fraction\n\nx = Fraction(1, 10)\ny = Fraction(2, 10)\nprint(x + y) # 3\/10<\/code><\/pre>\n\n\n\nThis avoids all floating-point inaccuracies entirely but may not be suitable for large-scale computations.<\/p>\n\n\n\n
Floating-Point Arithmetic Best Practices In Python<\/h2>\n\n\n\n
Floating-point inaccuracies are a result of binary representation, not a Python-specific issue. While such differences can be neglected in most cases, they can cause serious distrup they can cause serious concerns in comparisons or important applications.<\/p>\n\n\n\n
Best Practices:<\/strong><\/p>\n\n\n\n\n- Use round() for formatting float values<\/li>\n\n\n\n
- Use math.isclose() for safe float comparisons<\/li>\n\n\n\n
- Use decimal.Decimal for financial or high-precision applications<\/li>\n\n\n\n
- Use fractions.Fraction if exact arithmetic with ratios is required<\/li>\n<\/ul>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Python isn’t broken, floating-point math just has its quirks due to binary representation. If you’re working in finance, data science, or anything where precision matters, it\u2019s smart to handle float operations carefully. And if you’re looking to build accurate and reliable Python-based solutions, it’s a good idea to hire Python developers<\/a> who understand these nuances.<\/p>\n","protected":false},"excerpt":{"rendered":"At times simple arithmetic equations like 0.1+0.2 can give answers like 0.30000000000000004 instead of 0.3, in Python. Is Python broken then? No, this is not Python’s fault, it is the side effect of how floating numbers are represented in computers. Description of the Problem You\u2019re doing basic math in Python, but the results don\u2019t make […]<\/p>\n","protected":false},"author":2,"featured_media":2301,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[163,3],"tags":[],"class_list":["post-2299","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-python","category-web"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts\/2299","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/comments?post=2299"}],"version-history":[{"count":2,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts\/2299\/revisions"}],"predecessor-version":[{"id":2303,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts\/2299\/revisions\/2303"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/media\/2301"}],"wp:attachment":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/media?parent=2299"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/categories?post=2299"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/tags?post=2299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}