{{ message }}
Validate Locale parameter formats while constructing#309
Open
akx wants to merge 2 commits into
Open
Conversation
akx
force-pushed
the
validate-locale-ctor
branch
2 times, most recently
from
6cb6101 to
98a786d
Compare
Member
Author
|
Come to think of it, this paves the way nicely for #30; we can now derive a |
akx
force-pushed
the
validate-locale-ctor
branch
from
98a786d to
cf47d0a
Compare
Is there some kind of roadmap as to when fuzzy locales will be implemented? I have a requirement that needs the ability to define custom/fuzzy locales, so it would be great to know when I can implement this. |
akx
force-pushed
the
validate-locale-ctor
branch
from
cf47d0a to
b1ff3da
Compare
Member
Author
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
5 participants
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.
This avoids being able to construct mongrel locales with
language = 'en_US', territory = None.Fixes #283
This might actually be a fairly disruptive change to the users of the library who have come to expect they can build locales with
Locale("en_US").