Re: [Python-Dev] provisional status for asyncio

[Larry Hastings]

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.


Ultimately it's Larry's call, but I don't see why we couldn't. If we 
were talking about something as low-level as the urllib package then I 
would agree, but beyond its own tests is there anything in the stdlib 
that depends on asyncio?


I'm flexible here.  My concern is shipping high-quality software. 
Removing an entire package outright, even at such a late date, is pretty 
low-risk.  But before I'd allow it, you'd have to get a BDFL 
pronouncement (or BDFL-delegate pronouncement).



//arry/
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] provisional status for asyncio

[Yury Selivanov]

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 the standard library is something
that I don't think we can do so late in the 3.5 release candidates
process.


Ultimately it's Larry's call, but I don't see why we couldn't. If we 
were talking about something as low-level as the urllib package then 
I would agree, but beyond its own tests is there anything in the 
stdlib that depends on asyncio?


I'm flexible here.  My concern is shipping high-quality software. 
Removing an entire package outright, even at such a late date, is 
pretty low-risk.  But before I'd allow it, you'd have to get a BDFL 
pronouncement (or BDFL-delegate pronouncement).



//arry/


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/yselivanov.ml%40gmail.com


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] provisional status for asyncio

[Larry Hastings]

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 of work for a lot of people.


You could just hope for another Heartbleed bug,


//arry/
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] provisional status for asyncio

[Nick Coghlan]

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 the
> standard library on a provisional basis. Backwards
> incompatible changes (up to and including removal
> of the module) may occur if deemed necessary by the
> core developers.
>
> ?

I don't see much chance of us actually removing it - the most I see us
doing is potentially shifting to a "bundled 3rd party library" update
model if there's still a high churn rate in the API after another
release cycle.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com