This is a rather clickbaiting title... in truth it’s just that Python 2 doesn’t differentiate between strings and raw bytes by default. Nothing to do with IP (v4 or v6) addresses or the string “node.example.com”
Personally, I reserve "clickbait" for links with no substance or value on the other side of the click, but I understand what you mean.
Yes, the intent of the title is to get your attention, but I'm not trying to get you to buy anything, collecting or selling user data, etc.
I really just wrote the post to share a debugging experience I had this year. It doesn't have to do with IPv{4,6} addresses themselves or any specification thereof, but it does relate to the Python 2 `ipaddress` library's handling of them and a pitfall you can accidentally find yourself in.
A dry, but more accurate title might have been
Python 2's ipaddress library considers "node.example.com" an IPv6 Address
Comments
This is a rather clickbaiting title... in truth it’s just that Python 2 doesn’t differentiate between strings and raw bytes by default. Nothing to do with IP (v4 or v6) addresses or the string “node.example.com”
Personally, I reserve "clickbait" for links with no substance or value on the other side of the click, but I understand what you mean.
Yes, the intent of the title is to get your attention, but I'm not trying to get you to buy anything, collecting or selling user data, etc.
I really just wrote the post to share a debugging experience I had this year. It doesn't have to do with IPv{4,6} addresses themselves or any specification thereof, but it does relate to the Python 2 `ipaddress` library's handling of them and a pitfall you can accidentally find yourself in.
A dry, but more accurate title might have been