[issue40981] increment is wrong in 3.7 but not in 2.7

Steven D'Aprano added the comment: On Mon, Jun 15, 2020 at 07:37:16PM +, mike stern wrote: > sorry but I don't see the option to delete Your keyboard has a Delete key and a Backspace key. Select the quoted text in your email client and press one or the other. If you can't see the quoted

[issue40981] increment is wrong in 3.7 but not in 2.7

mike stern added the comment: sorry but I don't see the option to delete From: report=bugs.python@roundup.psfhosted.org on behalf of Terry J. Reedy Sent: Monday, June 15, 2020 11:46 AM To: rskir...@hotmail.com Subject: [issue40981] increment is wrong

[issue40981] increment is wrong in 3.7 but not in 2.7

Terry J. Reedy added the comment: Mike, when you respond by email, delete the text you are responding to. Your email is posted below the already posted text and the quote is useless noise that makes it harder to see what you wrote. Newcomers to Python who think they have seen a bug should

[issue40981] increment is wrong in 3.7 but not in 2.7

mike stern added the comment: I appreciate taking the time to explain , I just wished the other guys did that instead of just closing the ticket on my face. I wished at least they suggested me to use round() without any aggravations but thanks anyway From:

[issue40981] increment is wrong in 3.7 but not in 2.7

Steven D'Aprano added the comment: > I wouldn't trust a language behaving crazy like this I guess then you won't trust C, Java, C++, Swift, Javascript, Ruby, Cobol, Fortran, and pretty much every programming language in existence. The only ones that escape this are ones that don't have

[issue40981] increment is wrong in 3.7 but not in 2.7

mike stern added the comment: you can at least try it and see for yourself that what I am saying is actually true but never mind I will keep on opening tickets until someone tries it on 2.7 and see what I am talking about From: Redwane Freedom

[issue40981] increment is wrong in 3.7 but not in 2.7

mike stern added the comment: you can at least try it and see for yourself that what I am saying is actually true but never mind I will keep on opening tickets until someone tries it on 2.7 and see what I am talking about From: Redwane Freedom

[issue40981] increment is wrong in 3.7 but not in 2.7

mike stern added the comment: 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:

[issue40981] increment is wrong in 3.7 but not in 2.7

Christian Heimes 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

[issue40981] increment is wrong in 3.7 but not in 2.7

mike stern added the comment: Christian Heimes you haven't tried it on 2.7 did you ? -- status: closed -> open ___ Python tracker ___

[issue40981] increment is wrong in 3.7 but not in 2.7

Christian Heimes added the comment: Multiple people already told you that it is not a bug. It's how floating point standard IEEE 754 works. -- nosy: +christian.heimes status: open -> closed ___ Python tracker

[issue40981] increment is wrong in 3.7 but not in 2.7

Change by mike stern : -- nosy: -serhiy.storchaka, terry.reedy title: increment is wrong in 3.7 -> increment is wrong in 3.7 but not in 2.7 ___ Python tracker ___