I haven't read the bug, but given the extensive real-life use that ipaddr.py has seen at Google before inclusion into the stdlib, I think "deep conceptual flaws" must be an overstatement. There may be real differences of opinion about the politically correct way to view subnets and netmasks, but I don't doubt that the module as it stands is usable enough to keep it in the stdlib. Nothing's perfect.
I think we should just stick to "sorry, too late, try again for 3.2". We've done that with plenty of more important flaws that were discovered on the verge of a release, and I don't recall ever regretting it. We can always add more features to the module in 3.2. --Guido On Mon, Jun 1, 2009 at 11:32 AM, Raymond Hettinger <pyt...@rcn.com> wrote: > In http://bugs.python.org/issue3959 , Clay McClure is raising some > objections to the new ipaddr.py module. JP Calderone shares his concerns. > I think they were the only commenters not directly affiliated with one of > the competing projects. The issues they've raised seem serious, but I don't > know enough about the subject to make a meaningful comment. > > Am hoping python-dev participants can provide some informed judgments. At > issue is whether the module has some deep conceptual flaws that would > warrant pulling it out of the 3.1 release. Also at issue is whether the > addition was too rushed (see David Moss's comment on the tracker and later > comments by Antoine Pitrou). > > Does anyone here know if Clay's concern about subnets vs netmasks in > accurate and whether it affects the usability of the module? -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com