Re: [Python-Dev] provisional status for asyncio

On 30 August 2015 at 05:16, Yury Selivanov wrote: > Since there is at least some possibility that we might have another > discussion about asyncio removal from the stdlib in 3.6, should I > just reuse the warning we had in 3.4 for asyncio: > > > Note: The asyncio package has been included in t

Re: [Python-Dev] provisional status for asyncio

On 08/29/2015 12:18 PM, Yury Selivanov wrote: Larry, what will the release cycle for 3.5.x look like? Can we do bugfix releases every 3 or 4 months? It's usually more like every six. I've proposed doing them a little more frequently and gotten push back; a new Python release causes a bunch

Re: [Python-Dev] provisional status for asyncio

Larry, what will the release cycle for 3.5.x look like? Can we do bugfix releases every 3 or 4 months? Yury On 2015-08-29 1:36 PM, Larry Hastings wrote: On 08/28/2015 08:44 AM, Brett Cannon wrote: On Fri, 28 Aug 2015 at 08:35 Yury Selivanov wrote: Unfortunately, separating it from t

Re: [Python-Dev] provisional status for asyncio

On 08/28/2015 08:44 AM, Brett Cannon wrote: On Fri, 28 Aug 2015 at 08:35 Yury Selivanov > wrote: Unfortunately, separating it from the standard library is something that I don't think we can do so late in the 3.5 release candidates process. Ultimat