>>> I don't see any valid reason for entering a network as >>> "192.168.1.1/24" rather >>> than the canonical "192.168.1.0/24". The former might indicate a >>> typing error >>> or >>> a mental slip, so let's be helpful and signal it to the user. >> >> Or perhaps there can be an optional "strict=True" (or "strict=False") >> argument >> to the constructor / parsing function. > > If so, I hope that we'd default to strict=True. I don't see the point of enforcing strictness here. There are good use cases: if you know your address is 82.94.164.162, how do you compute what you should spell for 82.94.164.162/27? It's very easy to make a mistake here, and doing the computation in your head is really not something that should be necessary, given that a computer can get it correct easily. Regards, Martin
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