Movatterモバイル変換
[0]ホーム
[Python-Dev] PEP czar for PEP 3144?
Nick Coghlanncoghlan at gmail.com
Mon Feb 20 14:23:13 CET 2012
Does anyone object to me naming myself PEP czar for PEP 3144?I've collated the objections to the original proposal on a fewdifferent occasions throughout the (long!) PEP review process, and asnoted in the Background section, the latest version of the PEP [1] hasaddressed the key concerns that were raised:- the "strict" flag for Network objects is gone (instead, thevalidation differences between IP Network and IP Interface definitionsare handled as different classes with otherwise similar interfaces)- the factory function naming scheme follows PEP 8- some properties have been given new names that make it clearer whatkind of object they produce- the module itself has been given a new name (ipaddress) to avoidclashing with the existing ipaddr module on PyPIThere's also basic-but-usable module documentation available(http://code.google.com/p/ipaddr-py/wiki/Using3144).So, unless there are any new objections, I'd like to:- approve ipaddress for inclusion in Python 3.3- grant Peter Moody push access as the module maintainer- create a tracker issue to cover incorporating the new module intothe standard library, documentation and test suite(There are still a few places in both the PEP and the preliminarydocumentation that say "ipaddr" instead of "ipaddress", but those canbe cleaned up as the module gets integrated).I don't personally think the module API needs the provisionaldisclaimer as the core functionality has been tested for years inipaddr and the API changes in ipaddress are just cosmetic ones eitherfor PEP 8 conformance, or to make the API map more cleanly to theunderlying networking concepts. However, I'd be willing to includethat proviso if anyone else has lingering concerns.Regards,Nick.[1]http://www.python.org/dev/peps/pep-3144/-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
More information about the Python-Devmailing list
[8]ページ先頭