This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Wicken
Recipients Wicken
Date 2019-11-08.21:06:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573247171.82.0.693534364371.issue38750@roundup.psfhosted.org>
In-reply-to
Content
As alluded to in issue bpo-38655, the behaviour for getting categorising IPv4 networks is inconsistent with the IANA guideline, which the docs say it follows.

I'm proposing we either change the documentation so that it describes the behaviour that should actually be expected, or we rewrite some parts of the ipaddress module so that they follow the guidelines.

For the latter, my thoughts would be to actually implement the check table on the IANA page (https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml).

i.e for a given address, you can ask of it "is_forwardable", "is_globally_reachable", etc.
History
Date User Action Args
2019-11-08 21:06:11Wickensetrecipients: + Wicken
2019-11-08 21:06:11Wickensetmessageid: <1573247171.82.0.693534364371.issue38750@roundup.psfhosted.org>
2019-11-08 21:06:11Wickenlinkissue38750 messages
2019-11-08 21:06:11Wickencreate