[issue3959] Add Google's ipaddr.py to the stdlib

2009-01-03 Thread Duncan McGreggor
Duncan McGreggor added the comment: I am a contributor to netaddr, having deprecated my own old and crufty IP address library in its favor. JP's comments on the library in this ticket are included in the set of reasons that I initially chose it to replace my own. When I first looked a

[issue3959] Add Google's ipaddr.py to the stdlib

2009-01-03 Thread Duncan McGreggor
Duncan McGreggor added the comment: >> As for shutting down any project that is chosen, does such an action not >> leave older Python versions out in the cold? Shouldn't the project >> remain open to support Python versions < 2.7, with a highly visible note >&

[issue3959] Add Google's ipaddr.py to the stdlib

2009-02-02 Thread Duncan McGreggor
Duncan McGreggor added the comment: 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

[issue3959] Add Google's ipaddr.py to the stdlib

2009-02-04 Thread Duncan McGreggor
Duncan McGreggor added the comment: Antione, We're (netaddr) going to try to use ipaddr if possible, but there are operations which we are providing to API users that aren't directly supported by ipaddr. We haven't yet determined the level of effort involved in trying to wor

[issue3959] Add Google's ipaddr.py to the stdlib

2009-02-04 Thread Duncan McGreggor
Duncan McGreggor added the comment: > If changes to ipaddr could make things easier for netaddr's support > of advanced features, please do propose those changes! Thanks, Guido -- we will :-) We'll be watching closely for that and participating as