[issue27269] ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs

Changes by Alex Perry : -- pull_requests: +1831 ___ Python tracker ___ ___

[issue27269] ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs

Alex Perry added the comment: https://github.com/python/cpython/commit/5cc274262a99e5633177fc540261abbbecbbc51c ... seems to implement the principle in this bug, but I'm not convinced this is a good idea. -- nosy: +arp11 ___ Python tracker

[issue27269] ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs

Марк Коренберг added the comment: Also, it should be marked explicitly, if cross-type lookup is safe. I mean code like that: some_net = ipaddress.ip_network(some_input1) some_addr = ipaddress.ip_address(some_input2) return some_addr in some_net Is it safe to write such code? Docs

[issue27269] ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs

Марк Коренберг added the comment: see also issue20446 -- nosy: +mmarkk ___ Python tracker ___ ___

[issue27269] ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs

Changes by SilentGhost : -- nosy: +pmoody versions: -Python 3.3, Python 3.4 ___ Python tracker ___

[issue27269] ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs

New submission from ThiefMaster: I'd expect the IPv4 address to be considered part of that network (or actually parsed as an IPv4Address and not IPv6Address) even if it's written in IPv6 notation. It's an IPv4 after all. Python 3.5.1 (default, Jun 7 2016, 09:20:44) [GCC 4.9.3] on linux Type