René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ipaddress.IPv6Address.is_loopback broken for IPv4-mapped addresses","articleBody":"# Bug report\n\n### Bug description:\n\nWhile properties like `is_private` account for IPv4-mapped IPv6 addresses, such as for example:\n\n```python\n\u003e\u003e\u003e ipaddress.ip_address(\"192.168.0.1\").is_private\nTrue\n\u003e\u003e\u003e ipaddress.ip_address(\"::ffff:192.168.0.1\").is_private\nTrue\n```\n\n...the same doesn't currently apply to the `is_loopback` property:\n```python\n\u003e\u003e\u003e ipaddress.ip_address(\"127.0.0.1\").is_loopback\nTrue\n\u003e\u003e\u003e ipaddress.ip_address(\"::ffff:127.0.0.1\").is_loopback\nFalse\n```\n\nAt minimum, this inconsistency between different properties is counter-intuitive. Moreover, `::ffff:127.0.0.0/104` is for all intents and purposes a loopback address, and should be treated as such.\n\nFor the record, this will now match the behavior of other languages such as Rust, Go and .NET, cf. rust-lang/rust#69772.\n\n### CPython versions tested on:\n\nCPython main branch\n\n### Operating systems tested on:\n\nLinux\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-117567\n* gh-118391\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/paravoid","@type":"Person","name":"paravoid"},"datePublished":"2024-04-05T12:38:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/117566/cpython/issues/117566"}