Skip to content
New issue

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

Update idna to 2.8 #112

Closed
wants to merge 2 commits into from
Closed

Update idna to 2.8 #112

wants to merge 2 commits into from

Conversation

pyup-bot
Copy link
Collaborator

@pyup-bot pyup-bot commented Dec 4, 2018

This PR updates idna from 2.5 to 2.8.

Changelog

2.8

++++++++++++++++

- Update to Unicode 11.0.0.
- Provide more specific exceptions for some malformed labels.

2.7

++++++++++++++++

- Update to Unicode 10.0.0.
- No longer accepts dot-prefixed domains (e.g. ".example") as valid.
This is to be more conformant with the UTS 46 spec. Users should
strip dot prefixes from domains before processing.

2.6

++++++++++++++++

- Allows generation of IDNA and UTS 46 table data for different
versions of Unicode, by deriving properties directly from
Unicode data.
- Ability to generate RFC 5892/IANA-style table data
- Diagnostic output of IDNA-related Unicode properties and
derived calculations for a given codepoint
- Support for idna.__version__ to report version
- Support for idna.idnadata.__version__ and
idna.uts46data.__version__ to report Unicode version of
underlying IDNA and UTS 46 data respectively.
Links

@pyup-bot pyup-bot mentioned this pull request Dec 4, 2018
@jluebbe jluebbe force-pushed the master branch 2 times, most recently from d967c5f to fb55c92 Compare January 7, 2019 09:14
@jluebbe
Copy link
Owner

jluebbe commented Jun 12, 2019

Crossbar currently pins to idna 2.5.

@jluebbe jluebbe closed this Oct 27, 2019
@jluebbe jluebbe deleted the pyup-update-idna-2.5-to-2.8 branch October 27, 2019 18:24
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.

2 participants