REGEXES["no_vowels"] (^[^aeyiuo]+$, nameparser/config/regexes.py) is not referenced anywhere in the parser or the documentation sources. It was added in 4a6aa61 (Aug 2015) and appears never to have been used.
Beyond being dead weight, the pattern is misleading as public config: it's ASCII-only, so every non-Latin string ("Петров", "山田") matches "no vowels" — anyone reaching for it for its apparent purpose (detecting vowel-less abbreviations like "Dr") gets false positives on all non-Latin text.
Since C.regexes.no_vowels is technically public API surface, removal is a breaking change. Proposal: deprecate in a 1.x release (following the established 2.0 deprecation-warnings pattern from #253) and remove in 2.0.
REGEXES["no_vowels"](^[^aeyiuo]+$,nameparser/config/regexes.py) is not referenced anywhere in the parser or the documentation sources. It was added in 4a6aa61 (Aug 2015) and appears never to have been used.Beyond being dead weight, the pattern is misleading as public config: it's ASCII-only, so every non-Latin string ("Петров", "山田") matches "no vowels" — anyone reaching for it for its apparent purpose (detecting vowel-less abbreviations like "Dr") gets false positives on all non-Latin text.
Since
C.regexes.no_vowelsis technically public API surface, removal is a breaking change. Proposal: deprecate in a 1.x release (following the established 2.0 deprecation-warnings pattern from #253) and remove in 2.0.