Add runtime i18n hooks for validation messages#547
Open
aleksandr-kotlyar wants to merge 15 commits into
Open
Conversation
aleksandr-kotlyar
marked this pull request as ready for review
July 5, 2026 10:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds runtime i18n support for Voluptuous built-in validation messages.
This PR introduces gettext-compatible hooks so applications can translate Voluptuous error messages without Voluptuous shipping production translation catalogs.
Main changes:
configure_i18n()for loading gettext catalogs from an application-providedlocaledirset_gettext()for injecting a custom translation callablegettext_scope()for temporary context-local translation overridesInvalid.__str__message/error-type format through the i18n hook@ data[...], untranslated so existing tooling can continue to parse itVoluptuous intentionally does not ship production translation catalogs in this PR. Applications are expected to provide their own gettext catalogs.
Also includes a few small validation correctness fixes covered by tests while touching error-message paths:
NumberinputSchema.extend(Schema(...))Invalid.__repr__Resolves #73.