[- at google.com] this is what I wrote: it's not so much a need as it is useful. it's useful to take an address like 192.168.1.100/24 and derive a bunch of information from it (like the network address, broadcast address, containing supernets, etc), but still remember that the original address was 192.168.1.100. having a separate class or two for this is overly burdensome in my mind. FWIW, netaddr does the same thing. Cheers, /peter On Wed, Sep 30, 2009 at 2:34 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote: >> I don't know -- this is (from what Peter told me) a common use case so >> he (and presumably others) would from time to time have to write >> extra code to keep track of that IP address in a new app. > > I, and probably others, would really, REALLY like to see one such > "common use case". I do find it puzzling that non of the readers here > can think of any, and the continued assertion that use cases do exist > without them being presented is somewhat disturbing. > > Regards, > Martin > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev%40hda3.com >
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