Message163088
| Author |
ncoghlan |
| Recipients |
Ramchandra Apte, amak, eric.araujo, ezio.melotti, georg.brandl, giampaolo.rodola, hynek, ncoghlan, pmoody, python-dev, sandro.tosi, terry.reedy, tshepang |
| Date |
2012年06月18日.07:14:58 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1340003699.85.0.264274034254.issue14814@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
My current thoughts are to avoid the usual approach of embedding the method and property definitions in the class definitions, and instead have separate sections under [1] for
IP Addresses
IP Interfaces
IP Networks
Inside each of those sections, document the constructors directly under the section heading, and then separate out these subsections:
Common IP <kind> properties and methods
IPv4 <kind> properties and methods (if any)
IPv6 <kind> properties and methods (if any)
[1] http://docs.python.org/dev/library/ipaddress#representing-ip-addresses-and-networks |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年06月18日 07:14:59 | ncoghlan | set | recipients:
+ ncoghlan, georg.brandl, terry.reedy, giampaolo.rodola, amak, ezio.melotti, eric.araujo, pmoody, sandro.tosi, tshepang, python-dev, Ramchandra Apte, hynek |
| 2012年06月18日 07:14:59 | ncoghlan | set | messageid: <1340003699.85.0.264274034254.issue14814@psf.upfronthosting.co.za> |
| 2012年06月18日 07:14:59 | ncoghlan | link | issue14814 messages |
| 2012年06月18日 07:14:58 | ncoghlan | create |
|