Message78677
| Author |
pmoody |
| Recipients |
benjamin.peterson, drkjam, exarkun, giampaolo.rodola, gvanrossum, loewis, mattsmart, pmoody, shields, vstinner |
| Date |
2009年01月01日.02:00:15 |
| SpamBayes Score |
1.1592181e-08 |
| Marked as misclassified |
No |
| Message-id |
<1230775217.52.0.280972089133.issue3959@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
hm, all addresses have a subnet, even if its an implied /32, so
specifying a network as ("1.1.1.0", "1.1.1.255") seems a lot more
off-putting than "1.1.1.0/24". You're also much more likely to see the
latter in network devices. I guess I don't see the utility in an address
range of .1 - .22 (or something arbitrary, something which doesn't fall
on a power-of-2 boundary); when dealing with ranges of addresses, i've
always only wanted to/needed to manipulate sub-networks of addresses.
and my expectation was always that method names, etc. would have to be
converted to more closely match other python code; ipaddr was written to
google's python style guide, which I understand can be different than
the python.org style guide ;)
also, ipaddr does make extensive use of pydoc, but you're right, the
webpage is spartan.
happy (PST) new year.
Cheers,
/peter |
|