-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
gh-130167: Add a What's New entry for changes to textwrap.{de,in}dent
#131924
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
base: main
Are you sure you want to change the base?
Conversation
picnixz
left a comment
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.
There is a note:
Note that tabs and spaces are both treated as whitespace, but they are not
equal: the lines ``" hello"`` and ``"\thello"`` are considered to have no
common leading whitespace.
The new implementation still guarantees this right?
Doc/whatsnew/3.14.rst
Outdated
| characters other than space and tab. | ||
|
|
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.
Add something like (to be able to see the issue)
characters other than space and tab.
(Contributed by [...] in :gh:`...`.)
+ 2 blank lines to end the section.
textwrap.dedenttextwrap.dedent
Doc/whatsnew/3.14.rst
Outdated
|
|
||
| * Optimise the :func:`~textwrap.dedent` function, improving performance by | ||
| an average of 2.4x, with larger improvements for bigger inputs, | ||
| and fix a bug with incomplete normalization of blank lines with whitespace |
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.
Maybe use two separate bullet points for that? so that the reader is able to distinguish between a performance improvement and a behavioral change.
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.
Where should the second one go? Improved Modules is mainly for features, and a standalone bullet about the bugfix in Optimisations feels wrong.
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.
Well, I think it's still an improvement in some sense (even if we didn't treat it as a regular bugfix that we backport). For me I think that the behavioral change is important to note, hence I suggested using two separate bullet points (but still under the same section)
textwrap.dedenttextwrap.{de,in}dent
textwrap.{de,in}denttextwrap.{de,in}dent
|
@AA-Turner Can you also include the typo fix of the NEWS entry (https://github.com/python/cpython/pull/131923/files#r2044429846)? TiA |
|
Reminder for this :) |
serhiy-storchaka
left a comment
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. I have no opinion about normalised/normalized, please came to some conclusion.
(Was fixed in #132666) |
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
📚 Documentation preview 📚: https://cpython-previews--131924.org.readthedocs.build/
reuses #130167