➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Rhamphoryncus, benjamin.peterson, ezio.melotti, giampaolo.rodola, gregory.p.smith, gvanrossum, loewis, mattsmart, oubiwann, pitrou, pmoody, pnasrat, shields
Date 2009-02-04.18:02:12
SpamBayes Score 0.0011348372
Marked as misclassified No
Message-id <1233770533.77.0.503229956109.issue3959@psf.upfronthosting.co.za>
In-reply-to
Content 
Probably it has already been said, but for the record: is ipaddr's
current API ok for other libraries (mainly: netaddr) to build upon it
and provide compatible extensions or replacements, or would netaddr
become an incompatible alternative to the stdlib-provided ipaddr? The
latter would be a shame.
History
Date User Action Args
2009-02-04 18:02:14pitrousetrecipients: + pitrou, gvanrossum, loewis, gregory.p.smith, Rhamphoryncus, giampaolo.rodola, benjamin.peterson, ezio.melotti, mattsmart, shields, pmoody, pnasrat, oubiwann
2009-02-04 18:02:13pitrousetmessageid: <1233770533.77.0.503229956109.issue3959@psf.upfronthosting.co.za>
2009-02-04 18:02:12pitroulinkissue3959 messages
2009-02-04 18:02:12pitroucreate