-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
gh-87799: Improve the textual representation of IPv4-mapped IPv6 addresses #29345
Conversation
3117395
to
03cefda
Compare
@maxmouchet, @ykvch guys, please take a look on this PR when you get a chance. |
Thanks for tackling this! This looks good to me. Maybe the |
Thanks! Lets discuss it.
In addition, RFC 4007 Section 4 says that
That is all I managed to find regarding the subject. Please, let me know what you think about it. |
Noticed, that ipaddress.IPv6Address.exploded behavior differs from expected after the patch:
I'm in progress fixing that. |
This PR is stale because it has been open for 30 days with no activity. |
03cefda
to
b0f362c
Compare
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.
Ran 203 tests in 0.198s
OK
== Tests result: SUCCESS ==
And I get:
>>> addr.exploded '0000:0000:0000:0000:0000:ffff:8.8.4.4'
Looks good to me.
…esses Represent IPv4-mapped IPv6 address as x:x:x:x:x:x:d.d.d.d, where the 'x's are the hexadecimal values of the six high-order 16-bit pieces of the address, and the 'd's are the decimal values of the four low-order 8-bit pieces of the address (standard IPv4 representation).
68d0359
to
669cc90
Compare
@opavlyuk Could you sign the new CLA by clicking |
@arhadthedev Thanks for letting me know! I initially used the wrong SSH key for the commits, but I've fixed it and the CLA is now marked as signed. |
For now, we need to wait.
|
@arhadthedev Thanks for clearing things up! Then I'll watch out for the 3.12b1 release and return to the PR once all obstacles are cleared. |
@arhadthedev it appears a month has passed since the last update to the PR, during which time we haven't received further feedback. Also, I noticed that version 3.12.0a7 was released just yesterday. |
@encukou as you may recall, we had a conversation during PyCon SK 2022 where you kindly offered your guidance and support. I'm now writing to kindly ask if you could take a look at this PR. I would greatly appreciate your review, or if you could suggest someone who might be the right person for this task. Thank you for your time and consideration! |
@asvetlov could you please review this PR at your earliest convenience? |
The patch is good but I see a small problem.
According to RFC 4291 section 2.2 part 3 the representation should be Did I miss something? |
Ok, The It is doable but definitely not a part of this PR. |
@opavlyuk thanks for the patch! |
@asvetlov Apologies for the delayed response - I've just returned to my laptop after a long weekend and unfortunately missed your earlier comments. |
@asvetlov You're making good sense. Could you kindly provide some guidance on the best approach to address this, assuming it doesn't consume too much of your time? |
I don't think that a thread in python-ideas will draw attention. It is a relatively rarely used thing. You can just make a PR, and after a review it could be merged. The PR should contain the new property definition, using it in all places where It doesn't sound like a lot of work. |
https://bugs.python.org/issue43633