-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Remove octal/hexadecimal parsing from IPv4. Fixes #9187 #19811
Conversation
@@ -148,6 +148,11 @@ end | |||
|
|||
# Parsing | |||
|
|||
const ipv4_leading_zero_error = """ | |||
Leading zeros in IPv4 addresses are disallowed due to ambiguity. | |||
If octal or hexadecimal, convert to decimal, otherwise remove leading zero. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO this reads kind of weird, since the first sentence is a complete sentence and this one isn't. Perhaps the second could be rephrased as
If the address is in octal or hexadecimal, convert it to decimal, otherwise remove the leading zero.
?
This is technically a breaking change, right? So I guess it would have to be noted as such in NEWS? |
Marking as 0.6.0 since this seems mostly ready to go. |
Would be gentler to have this go through a deprecation cycle, if possible. |
I think uses of this syntax are so incredibly rare and marginal that we can just remove support. |
@ararslan do you want to push a rewording here then? |
@tkelman The deed is done. |
Needs a NEWS entry in the breaking changes section. |
No description provided.