Skip to content

docs: fix multiple 'exampele' typos in email parser tests#148561

Closed
alideniztartma wants to merge 1 commit intopython:mainfrom
alideniztartma:fix/misspelled-example-in-tests
Closed

docs: fix multiple 'exampele' typos in email parser tests#148561
alideniztartma wants to merge 1 commit intopython:mainfrom
alideniztartma:fix/misspelled-example-in-tests

Conversation

@alideniztartma
Copy link
Copy Markdown

Fixed multiple occurrences in test_email where example.com was misspelled as exampele.com.

This is a trivial typo fix in the test suite to ensure consistency across email parser test cases. No issue number is required for this change.

Fixed multiple occurrences where 'example.com' was written as 'exampele.com'.
This ensures consistency across email address test cases.
@alideniztartma alideniztartma requested a review from a team as a code owner April 14, 2026 16:22
@python-cla-bot
Copy link
Copy Markdown

python-cla-bot bot commented Apr 14, 2026

All commit authors signed the Contributor License Agreement.

CLA signed

@bedevere-app bedevere-app bot added the tests Tests in the Lib/test dir label Apr 14, 2026
@bedevere-app
Copy link
Copy Markdown

bedevere-app bot commented Apr 14, 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.

@alideniztartma alideniztartma changed the title docs: fix multiple 'exampele' typos in email parser tests docs: fix multiple 'exampele' typos in email parser tests (skip issue) Apr 14, 2026
@alideniztartma alideniztartma changed the title docs: fix multiple 'exampele' typos in email parser tests (skip issue) docs: fix multiple 'exampele' typos in email parser tests Apr 14, 2026
@StanFromIreland
Copy link
Copy Markdown
Member

As this is in tests, it makes no difference and as such is a cosmetic change. Per the devguide, I'm afraid we don't accept these.

@alideniztartma
Copy link
Copy Markdown
Author

Thanks for the feedback! I missed that part of the devguide. Totally makes sense, won't happen again. Cheers!

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

Labels

awaiting review tests Tests in the Lib/test dir

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants