Skip to content

Fix incorrect isinstance check in parse_name_and_email_list#176

Merged
lavr merged 1 commit intomasterfrom
fix/issue-167-name-email-tuple-check
Mar 30, 2026
Merged

Fix incorrect isinstance check in parse_name_and_email_list#176
lavr merged 1 commit intomasterfrom
fix/issue-167-name-email-tuple-check

Conversation

@lavr
Copy link
Copy Markdown
Owner

@lavr lavr commented Mar 30, 2026

Summary

  • Fix typo on line 134 of emails/utils.py: isinstance(e, string_types) was checked twice instead of checking n in the second test, causing the name type validation to be silently skipped.

Fixes #167

@lavr lavr force-pushed the fix/issue-167-name-email-tuple-check branch from 19ac7a2 to 8d72705 Compare March 30, 2026 22:04
The condition on line 134 was checking `isinstance(e, string_types)`
twice instead of checking `n` in the second test. This caused the
name type validation to be silently skipped.

Fixes #167
@lavr lavr force-pushed the fix/issue-167-name-email-tuple-check branch from 8d72705 to f1e81eb Compare March 30, 2026 22:06
@lavr lavr merged commit add10ce into master Mar 30, 2026
4 checks passed
@lavr lavr deleted the fix/issue-167-name-email-tuple-check branch March 30, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Possibly incorrect test when checking for (name, email) tuple

1 participant