-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
gh-119447: Fix build with _PY_SHORT_FLOAT_REPR == 0 #121178
Conversation
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…21178) (cherry picked from commit c3677be) Co-authored-by: Yureka <[email protected]>
GH-121179 is a backport of this pull request to the 3.13 branch. |
Sorry, @yu-re-ka and @vstinner, I could not cleanly backport this to
|
Also needs back port to 3.12. The diff for that is available here: https://github.com/yu-re-ka/nixpkgs/blob/27fa2eb77ee683db4e9318d58c5fe102b25cfb6e/pkgs/development/interpreters/python/cpython/3.12/0001-Fix-build-with-_PY_SHORT_FLOAT_REPR-0.patch |
GH-121180 is a backport of this pull request to the 3.12 branch. |
) (cherry picked from commit c3677be)
Right. I created a PR manually for 3.12 using a cherry-pick of your fix: #121180. |
After 3c57971 the dtoa_runtime_state is referenced from pycore_runtime.h (later moved to Include/internal/pycore_interp.h) unconditionally, but the dtoa_runtime_state struct is not defined in all cases. Use the "not_used" definition of dtoa_runtime_state which already exists for the Py_USING_MEMORY_DEBUGGER case on those platforms as well.