exarkun at twistedmatrix.com wrote: > On 11:10 am, ncoghlan at gmail.com wrote: >> If the default IPNetwork constructor was made more strict, then this >> functionality would have to be made available another way (probably as >> an alternate constructor like IPNetwork.from_host_address rather than as >> a boolean 'strict' option) > > This seems to be the right solution to me, particularly the use of an > alternate constructor rather than an ambiguously named flag. Particular since someone pointed out that the "Network" object was remembering which IP address happened to be passed to the constructor (which is "Address with Mask" behaviour, as has been mentioned). That said, I've been trying to refrain from commenting on specifics of the API, as I haven't tried to use it for anything. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
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