You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2021-02-26.04:24:28.135>created_at=<Date2021-02-20.17:02:21.528>labels= ['expert-C-API', 'type-bug']
title="unnecessary leading '\\n' from Py_GetCompiler() when build with different complier"updated_at=<Date2021-02-26.04:24:28.134>user='https://github.com/josephsmeng'
The function Py_GetCompiler() return the version info with a leading '\n' when build with GCC/clang, while without this on other compilers. This inconsistent make the REPL print the 'welcome message' quit different, which I think is not we expect.
From the snapshot images, we can see, when compiler with MSVC, the 'welcome message' has two lines, but with GCC it is 3 lines, which two lines is what expected.
Patch is given in the github rp, thanks for review.
josephsmengmannequin
changed the title
Inconsistent behavior of Py_GetCompiler()
unnecessary leading '\n' from Py_GetCompiler() when build with different complier
Feb 21, 2021
josephsmengmannequin
changed the title
Inconsistent behavior of Py_GetCompiler()
unnecessary leading '\n' from Py_GetCompiler() when build with different complier
Feb 21, 2021
Right now there is no need to keep this limits, and the __version__ info from GCC is quite simple. Pls the attached snapshot image.
Therefor I don't think we should keep a commit from 2000.
New changeset 28a30bc by Joseph Shen in branch 'master':
closes bpo-43278: remove unnecessary leading '\n' from COMPILER when build with GCC/Clang (GH-24606) 28a30bc
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: