Author oubiwann
Recipients Rhamphoryncus, benjamin.peterson, drkjam, exarkun, ezio.melotti, giampaolo.rodola, gvanrossum, loewis, mattsmart, oubiwann, pitrou, pmoody, pnasrat, shields
Date 2009-02-02.22:14:39
SpamBayes Score 0.00298813
Marked as misclassified No
Message-id <1233612881.5.0.966405928675.issue3959@psf.upfronthosting.co.za>
In-reply-to
Content
Well, here are my thoughts on the matter:
 * ipaddr is relatively small, fast, and focuses on some core functionality
 * netaddr is designed to be very flexible (sometimes at the cost of a
little speed), leaning more towards a network calculation/address
manipulation "framework"

As such, and given the recent work made to ipaddr to make it
stdlib-friendly, my vote would be to include ipaddr in Python while
netaddr can continue growing, providing its user base with diverse
functionality while hopefully taking advantage of ipaddr in the Python
stdlib as much as is practical and useful.
History
Date User Action Args
2009-02-02 22:14:41oubiwannsetrecipients: + oubiwann, gvanrossum, loewis, exarkun, Rhamphoryncus, pitrou, giampaolo.rodola, benjamin.peterson, ezio.melotti, mattsmart, shields, pmoody, pnasrat, drkjam
2009-02-02 22:14:41oubiwannsetmessageid: <1233612881.5.0.966405928675.issue3959@psf.upfronthosting.co.za>
2009-02-02 22:14:40oubiwannlinkissue3959 messages
2009-02-02 22:14:40oubiwanncreate