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
C language typos #95969
Comments
Labels for this ticket might be adjusted/corrected. |
a typo was corrected upstream today in pysqlite the file appears in this repo as Modules/_sqlite/cursor.c quickly lookup context where the typo(s) appear
redirect output
if the following line is uncommented
remove backslashes
then run
|
Thanks for you interest in improving CPython. Typos in source code comments are not bugs; I'm removing the bug label. AFAIK, no-one has misunderstood the meaning of the misspelled words. Fixing them is churn for very little benefit. I suggest to leave them in place and close this issue. |
See also #93124 (comment) |
should have opened a blank issue a Documentation label when code and comment changes are involved doesn't sit well with me
as others from different coding language communities may read the source files the changes are indicated |
found another .c file typo
this is a repo wide bulk fix for C language typos a brief perusal of Lib top-level .py files revealed a few typos replacement strings becoming
A Philosophy of Software Design 12 Why Write Comments? The Four Excuses |
Closing this for the reasons provided in #95969 (comment) and #93124 (comment) |
PR
updated Nov 6, 2022 Implemented in effect with merge of PR
|
ghost commentedAug 13, 2022
•
edited by ghost
A Member can decide whether to uncomment the lines in the script.
grep -nr UNMARSHALLABLE cpython
grep -nr unmarshallable cpython
grep -n *p*redicate cpython/Python/getargs.c
I would leave it to someone else to open a PR.
The text was updated successfully, but these errors were encountered: