[Python-Dev] Open PEPs and large-scale changes for 3.3 (original) (raw)
Eli Bendersky eliben at gmail.com
Tue May 1 17:12:52 CEST 2012
- Previous message: [Python-Dev] Open PEPs and large-scale changes for 3.3
- Next message: [Python-Dev] Open PEPs and large-scale changes for 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, May 1, 2012 at 16:43, Benjamin Peterson <benjamin at python.org> wrote:
2012/5/1 Eli Bendersky <eliben at gmail.com>:
Will this package go through the provisional state mandated by PEP 411 ? I don't see PEP 411 requiring any module to go through its process.
You're right, it doesn't require it. However, since Nick's summary above mentioned a "draft API", I thought this package can be a good candidate for a PEP-411-process. Without PEP 411, once a module gets into stdlib, its API is pretty much locked. If we are wary of such lock-in with the current state ipaddr's API is in, PEP 411 seems like a reasonable way to go.
Eli
- Previous message: [Python-Dev] Open PEPs and large-scale changes for 3.3
- Next message: [Python-Dev] Open PEPs and large-scale changes for 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]