This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: error past 15 places
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 3.6
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: Whitequill Riclo, tim.peters, zach.ware
Priority: normal Keywords:

Created on 2019-07-31 04:19 by Whitequill Riclo, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (4)
msg348775 - (view) Author: Whitequill Riclo (Whitequill Riclo) Date: 2019-07-31 04:19
I have found that when doing the calculation when running:

pow(1 + 1/100000000000000, 100000000000000) = 2.716110034087023

pow(1 + 1/1000000000000000, 1000000000000000) = 3.03503520654962

This is incorrect as the following is a well known way to calculate Euler's number.
I do not know what component is the cause so I just picked one.
msg348776 - (view) Author: Whitequill Riclo (Whitequill Riclo) Date: 2019-07-31 04:24
This error happens in Google's search too which means that Google is using Python server-side and some how this hasn't been addressed.
msg348784 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2019-07-31 05:20
This is a limitation of binary floating point, please see https://docs.python.org/3/tutorial/floatingpoint.html
msg348787 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2019-07-31 05:24
You'll see much the same in every programming language that supports your computer's floating-point hardware.  Start by reading this gentle introduction:

https://docs.python.org/3/tutorial/floatingpoint.html

This bug tracker isn't a place for tutorials, though, and understanding floating-point deeply is a massive undertaking.
History
Date User Action Args
2022-04-11 14:59:18adminsetgithub: 81908
2019-07-31 05:24:08tim.peterssetnosy: + tim.peters
messages: + msg348787
2019-07-31 05:20:53zach.waresetstatus: open -> closed

nosy: + zach.ware
messages: + msg348784

resolution: not a bug
stage: resolved
2019-07-31 04:24:41Whitequill Riclosetmessages: + msg348776
2019-07-31 04:19:02Whitequill Riclocreate