Le mardi 15 septembre 2009 à 15:48 -0400, R. David Murray a écrit :
>
> It's useful functionality is parsing/validating an address+mask, rendering
> as address+mask, and being able to get the associated IP and network objects
> from it. It's a small class, but useful, IMO.
If it's only about parsing and validating, then a tuple works just fine.
Getting the associated IP objects is obtained from iterating over the
network.
Getting the associated network objects I don't understand. There is a
single network, not a bunch of them.
> However, I do not think
> that the proposed API should accept, eg, IPv4Network('192.168.1.1/24')
> as valid. That's just too confusing and error prone.
Indeed, it should throw some kind of ValueError instead.
> Oh, and if people don't like 'zero' as the name for the IPv4Address
> at the beginning of the network IP range, how about 'network_ip' or
> 'network_address' instead of just network, to make it clearer that it
> is an address?
How about something more explicit about how it's obtained, like
'lower_bound'?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4