Skip to content

Conversation

@whyvineet
Copy link

@whyvineet whyvineet commented Jan 26, 2026

@bedevere-app
Copy link

bedevere-app bot commented Jan 26, 2026

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

@bedevere-app
Copy link

bedevere-app bot commented Jan 26, 2026

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

@sergey-miryanov
Copy link
Contributor

It is not user facing, so I'm not sure it is worth to do.

@sergey-miryanov
Copy link
Contributor

cc @StanFromIreland @hugovk

@picnixz
Copy link
Member

picnixz commented Jan 26, 2026

This is code churn, it's not user-facing and it requires to regenerate the configure script and configure.ac. So I don't think it's worth it. Sorry, but I'm closing it. Please read the devguide to know what are acceptable issues. If it's not in the devguide, the general rule for typos is:

Typos are only corrected if they are user-facing (e.g., rST docs, or docstrings of library code: we don't care about typos in tests unless they are really important (e.g., the comment is wrong)).

@picnixz picnixz closed this Jan 26, 2026
@whyvineet
Copy link
Author

Sure @picnixz, I didn’t find a specific mention of this in the devguide, but I agree this typo isn’t user-facing. I’ll keep this in mind for future contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Typo in configure comment

3 participants