-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
bpo-44734: Fix floating point precision in test_turtle #30910
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
Conversation
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
(cherry picked from commit aa78287) Co-authored-by: Karolina Surma <33810531+befeleme@users.noreply.github.com>
(cherry picked from commit aa78287) Co-authored-by: Karolina Surma <33810531+befeleme@users.noreply.github.com>
GH-30960 is a backport of this pull request to the 3.10 branch. |
GH-30961 is a backport of this pull request to the 3.9 branch. |
|
The buildbot failure in test_ftplib definitely looks unrelated. The next build (also of the main branch) succeeded. test_ftplib seems a bit flaky on this buildbot: https://buildbot.python.org/all/#/builders/725 |
(cherry picked from commit aa78287) Co-authored-by: Karolina Surma <33810531+befeleme@users.noreply.github.com>
Hello,
for context, we ran across the problematic test in Fedora, when older Pythons stopped building on 32-bit because of the strict assert. The patch made it build again. We haven't spotted the failure from Python 3.7 above.
The test failure is known: here and here. The changes in the turtle module code prevent the test from failing but it was pointed out that still the test is unnecessarily strict and it's better to have it relaxed.
The referred issue was already fixed for one of the two problematic asserts.
https://bugs.python.org/issue44734