[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

pmoody added the comment: If you have the ability to use cidr, then closing this as wontfix is my preference. I've heard that there might be some network vendors that are starting support the mask notation for v6 addresses though, so this may end up getting implemented at some point in future

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

Chris PeBenito added the comment: I understand the resistance; I'm fine closing this as "won't implement", though this is not for academic use. In a nutshell, my package currently has a set of classes to represent an SELinux policy, and the SELinux policy language represents networks with ext

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

pmoody added the comment: Hey Chris, What's the usecase for this? the netmask notation doesn't appear to be common for v6 (at all), so I'm hesitant to add support for this if it's just something like an academic exercise. Cheers, peter -- ___ Pyth

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

pmoody added the comment: > # We only support CIDR for IPv6, because expanded netmasks are not > # standard notation. Yes, that's correct. I can double check this, but when I wrote ipaddress, I had yet to encounter a v6 netmask in anything other than cider notation. -- ___

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

Antoine Pitrou added the comment: I don't know enough about IPv6 to give more insight (perhaps Peter Moody can answer), but the tests have this comment: # We only support CIDR for IPv6, because expanded netmasks are not # standard notation. -- ___

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

Chris PeBenito added the comment: That's unfortunate. The library provides factory functions so v4 and v6 addresses/networks are easily handled together, and yet it seems to have been overlooked that you can do this: ipaddress.ip_network('192.168.1.0/255.255.255.0') but not this: ipaddress.

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

Antoine Pitrou added the comment: The doc is unhelpful on this, but looking at the implementation and tests, only a prefix length is allowed, not an expanded netmask. This would therefore be a feature request. -- type: behavior -> enhancement versions: -Python 3.4 ___

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

Changes by Antoine Pitrou : -- versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

Changes by Raymond Hettinger : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

Changes by Ned Deily : -- nosy: +ncoghlan, pmoody ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue22800] IPv6Network constructor sometimes does not recognize legitimate netmask

New submission from Chris PeBenito: Python 3.3/3.4 sometimes does not recognize a legitimate IPv6Network netmask: $ python3 Python 3.3.5 (default, May 28 2014, 13:56:57) [GCC 4.7.3] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import ipaddress as ip >>> no