Dear All,
I have not received any responses since my first post in this thread in
September last year. This time I am adding python-dev to BCC in hopes to
reach a larger audience. With the date of the first beta (2016-09-07) fast
approaching, I would like to commit PEP 495 implementation hopefu
On 06/28/2016 04:23 PM, Raymond Hettinger wrote:
On Jun 29, 2016, at 12:42 AM, Larry Hastings wrote:
By the way, I don't know why you Cc'd Nick and Brett. While they're fine
fellows, they aren't on the release team, and they aren't involved in these
sorts of decisions.
We're all involved in
> On Jun 29, 2016, at 12:42 AM, Larry Hastings wrote:
>
> By the way, I don't know why you Cc'd Nick and Brett. While they're fine
> fellows, they aren't on the release team, and they aren't involved in these
> sorts of decisions.
We're all involved in those sort of decisions.
Raymond
On 06/28/2016 02:05 PM, Yury Selivanov wrote:
Larry and the release team: would it be possible to make an
"emergency" 3.5.3 release?
I'd like to hear from the other asyncio reviewers: is this bug bad
enough to merit such an "emergency" release?
Thanks,
//arry/
___
On 06/28/2016 02:05 PM, Yury Selivanov wrote:
Long story short, I've discovered that asyncio is broken in 3.5.2.
Specifically, there is a callbacks race in `loop.sock_connect` which
can make subsequent `loop.sock_sendall` calls to hang forever. This
thing is very tricky and hard to detect and de
On Jun 28, 2016 2:56 PM, "Guido van Rossum" wrote:
>
> Awesome. That addresses my last concerns. PEP 520 is now accepted.
> Congratulations!
Yay! Thank you and to all those that gave such good feedback.
-eric (phone)
___
Python-Dev mailing list
Python
Long story short, I've discovered that asyncio is broken in 3.5.2.
Specifically, there is a callbacks race in `loop.sock_connect` which
can make subsequent `loop.sock_sendall` calls to hang forever. This
thing is very tricky and hard to detect and debug; I had to spend a
few hours investigating wh
On 06/28/2016 01:55 PM, Guido van Rossum wrote:
Awesome. That addresses my last concerns. PEP 520 is now accepted.
Congratulations!
And more Congratulations!!
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mail
Awesome. That addresses my last concerns. PEP 520 is now accepted.
Congratulations!
On Tue, Jun 28, 2016 at 1:43 PM, Eric Snow wrote:
> On Tue, Jun 28, 2016 at 11:43 AM, Guido van Rossum wrote:
>> On Tue, Jun 28, 2016 at 10:30 AM, Eric Snow
>> wrote:
>>> I suppose I'm having a hard time lettin
On Tue, Jun 28, 2016 at 11:43 AM, Guido van Rossum wrote:
> On Tue, Jun 28, 2016 at 10:30 AM, Eric Snow
> wrote:
>> I suppose I'm having a hard time letting go of the attractiveness of
>> "read-only == complete". However, given that you've been pretty clear
>> what you think, I'm more at ease a
On Tue, Jun 28, 2016 at 10:30 AM, Eric Snow wrote:
> On Sun, Jun 26, 2016 at 5:55 PM, Guido van Rossum wrote:
>>> On Fri, Jun 24, 2016 at 4:37 PM, Nick Coghlan wrote:
>>> > This version looks fine to me.
>>
>> Same to me, mostly.
>
> I've updated the PEP per everyone's comments [1], except I sti
On Sun, Jun 26, 2016 at 5:55 PM, Guido van Rossum wrote:
>> On Fri, Jun 24, 2016 at 4:37 PM, Nick Coghlan wrote:
>> > This version looks fine to me.
>
> Same to me, mostly.
I've updated the PEP per everyone's comments [1], except I still
haven't dropped the read-only __definition_order__ constra
12 matches
Mail list logo
