We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, both representations are valid. But we should convert them to only one representation, avoiding duplicates.
>>> harm.FQDN.is_valid('ö1.at') True >>> harm.FQDN.is_valid('xn--1-0ga.at') True
The text was updated successfully, but these errors were encountered:
Mobile
On 28.07.2016, at 15:00, Sebastian notifications@github.com wrote: Currently, bot representations are valid. But we should convert them to only one representation, avoiding duplicates. harm.FQDN.is_valid('ö1.at') True harm.FQDN.is_valid('xn--1-0ga.at') True
On 28.07.2016, at 15:00, Sebastian notifications@github.com wrote:
Currently, bot representations are valid. But we should convert them to only one representation, avoiding duplicates.
harm.FQDN.is_valid('ö1.at') True harm.FQDN.is_valid('xn--1-0ga.at') True
You mean normalize ? I am for the xn-- standard in this case.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Sorry, something went wrong.
okay, decision: normalisation is IDN ("xn--" format)
@aaronkaplan +1 ;)
BUG: FQDNs in IDN format
3342a23
fixes #622 Signed-off-by: Sebastian Wagner <sebix@sebix.at>
sebix
No branches or pull requests
Currently, both representations are valid. But we should convert them to only one representation, avoiding duplicates.
The text was updated successfully, but these errors were encountered: