Skip to content

Fix ASCII position in description of curses.ascii.rst #129300

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rffontenelle
Copy link
Contributor

@rffontenelle rffontenelle commented Jan 25, 2025

This makes sure the "ASCII" word in these descriptions are in the same place as in other nearby descriptions: an/any ASCII something letter/character. For instance, any ASCII printable character and an ASCII uppercase letter.


📚 Documentation preview 📚: https://cpython-previews--129300.org.readthedocs.build/

@bedevere-app bedevere-app bot added awaiting review docs Documentation in the Doc dir skip news labels Jan 25, 2025
@@ -148,7 +148,7 @@ C library:

.. function:: ispunct(c)

Checks for any printable ASCII character which is not a space or an alphanumeric
Checks for any ASCII printable character which is not a space or an alphanumeric
Copy link
Member

@StanFromIreland StanFromIreland Jan 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Checks for any ASCII printable character which is not a space or an alphanumeric
Checks for any printable ASCII character which is not a space or an alphanumeric

I think the current state here is fine, it reads normally.

Other change however is an error and I think it should be merged.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree it reads normally, but did you see that other descriptions are like "any ASCII printable character" and "an ASCII uppercase letter" ? Keeping this as "any printable ASCII character" would make it sort of uneven

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

2 participants