[Python-Dev] Breaking up the stdlib (Was: release cadence)
Steve Dower
steve.dower at python.org
Wed Jul 6 12:26:54 EDT 2016
More information about the Python-Dev mailing list
Wed Jul 6 12:26:54 EDT 2016
- Previous message (by thread): [Python-Dev] Breaking up the stdlib (Was: release cadence)
- Next message (by thread): [Python-Dev] Making stdlib modules optional for distributions (Was: Breaking up the stdlib (Was: release cadence))
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 06Jul2016 0753, Steve Dower wrote: > Thrashing out details should go on the workflow SIG, and I guess I'm the > obvious candidate to push it asking. But given my own time constraints > right now, I'm not going to dive into details if the high level concept > (stdlib packages can be individually updated by end users apart from a > full CPython release) is at issue. > > Once there seems to be general agreement that this is a worthy goal, > I'll see if I can put down details for how I would implement it. (And go > join the core-workflow list, I guess :) ) Rather than wait for general agreement, since this thread is probably widely muted already, I'll put a PEP together to clearly set out what I'm envisioning here in a form we can directly discuss. But time is precious, so don't expect it this week :) (Also, on Brett's advice, this belongs on python-dev and not core-workflow right now.) Cheers, Steve
- Previous message (by thread): [Python-Dev] Breaking up the stdlib (Was: release cadence)
- Next message (by thread): [Python-Dev] Making stdlib modules optional for distributions (Was: Breaking up the stdlib (Was: release cadence))
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list