GeezerVison is showing github.com — gh-143930: Fix typo in NEWS entry by benediktjohannes · Pull Request #147948 · python/cpython
Conversation
benediktjohannes
commented
Mar 31, 2026
•
edited by bedevere-app
Bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
We do always include a "." at the end of the Whats New statement in the release notes (see
gh-143935: Fixed a bug in the folding of comments when flattening an email message using a modern email policy. Comments consisting of a very long sequence of non-foldable characters could trigger a forced line wrap that omitted the required leading space on the continuation line, causing the remainder of the comment to be interpreted as a new header field. This enabled header injection with carefully crafted inputs.
gh-143925: Reject control characters in data: URL media types.
gh-143919: Reject control characters in http.cookies.Morsel fields and values.
gh-143916: Reject C0 control characters within wsgiref.headers.Headers fields, values, and parameters.
)
And Benedikt Tran said that it's not necessary to open up an issue for just fixing a typo, but I don't know whether formating of the title is correct now because of the missing issue
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Please apply skip issue, thanks!
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
picnixz
changed the title
[No issue, just a typo]: Add "." in release notes statement
gh-143930: Fix typo in NEWS entry
Mar 31, 2026
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I don't think it's actually worth it. The NEWS entry was backported to security branches, so I prefer that it's amended in #146476 directly.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Please apply skip issue, thanks!
As I said in the past, let maintainers decide what labels to add. Don't ask them please. In this case, a skip issue would not be correct and the change itself was not motivating enough as it would have required backports to security branches.
|
benediktjohannes reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Please apply skip issue, thanks!
As I said in the past, let maintainers decide what labels to add. Don't ask them please. In this case, a skip issue would not be correct and the change itself was not motivating enough as it would have required backports to security branches.
Ah, thank you for telling me about this, it's a good idea to use the other PR for this! 👍
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
And sorry for the label comment, I didn't ping anyone for this, I just thought that this label was correct and needed because the check failed, sorry, now I know for the future!
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|