Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-31373: remove overly strict float range checks #3486

Merged
merged 1 commit into from
Sep 11, 2017

Conversation

benjaminp
Copy link
Contributor

@benjaminp benjaminp commented Sep 10, 2017

This undoes a853a8b except for the pytime.c
parts. We want to continue to allow IEEE 754 doubles larger than FLT_MAX to be
rounded into finite floats. Tests were added to very this behavior.

https://bugs.python.org/issue31373

This undoes a853a8b except for the pytime.c
parts. We want to continue to allow IEEE 754 doubles larger than FLT_MAX to be
rounded into finite floats. Tests were added to very this behavior.
Copy link
Member

@mdickinson mdickinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@benjaminp benjaminp merged commit 2bb69a5 into master Sep 11, 2017
benjaminp added a commit that referenced this pull request Sep 11, 2017
This undoes a853a8b except for the pytime.c
parts. We want to continue to allow IEEE 754 doubles larger than FLT_MAX to be
rounded into finite floats. Tests were added to very this behavior.
(cherry picked from commit 2bb69a5)
@benjaminp benjaminp deleted the benjamin-float-rounding branch September 12, 2017 06:08
benjaminp added a commit that referenced this pull request Sep 12, 2017
…3495)

This undoes a853a8b except for the pytime.c
parts. We want to continue to allow IEEE 754 doubles larger than FLT_MAX to be
rounded into finite floats. Tests were added to very this behavior.
(cherry picked from commit 2bb69a5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants