➜

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.

Author rskiredj@hotmail.com
Recipients christian.heimes, rskiredj@hotmail.com
Date 2020-06-15.06:45:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <BN8PR20MB25645A275BF28312729602A0D59C0@BN8PR20MB2564.namprd20.prod.outlook.com>
In-reply-to <1592203232.19.0.491906136749.issue40981@roundup.psfhosted.org>
Content 
what is rude is to talk to me in an autoritative way like you do
you haven't even checked what I said , I said it working in Python 2.7 and it is not in 3.7
and you want to just read me an article.

________________________________
From: report=bugs.python.org@roundup.psfhosted.org <report=bugs.python.org@roundup.psfhosted.org> on behalf of Christian Heimes <report@bugs.python.org>
Sent: Monday, June 15, 2020 2:40 AM
To: rskiredj@hotmail.com <rskiredj@hotmail.com>
Subject: [issue40981] increment is wrong in 3.7 but not in 2.7

Christian Heimes <lists@cheimes.de> added the comment:

Python's float are IEE 754 floats for over 25 years and since Python 1.x, maybe earlier. IIRC standard is from 1985. It's how CPUs have dealt with floats for over 35 years.

By the way it's is incredible rude to keep re-opening a bug and responding on a closed bug. Do not reopen the bug again.

----------
status: open -> closed

_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue40981>
_______________________________________
History
Date User Action Args
2020-06-15 06:45:27rskiredj@hotmail.comsetrecipients: + rskiredj@hotmail.com, christian.heimes
2020-06-15 06:45:27rskiredj@hotmail.comlinkissue40981 messages
2020-06-15 06:45:27rskiredj@hotmail.comcreate