On Jul 03, 2016, at 01:17 AM, Ludovic Gasc wrote:
>If 3.5.2.1 or 3.5.3 are impossible to release before december, what are the
>alternative solutions for AsyncIO users ?
>1. Use 3.5.1 and hope that Linux distributions won't use 3.5.2 ?
Matthias just uploaded a 3.5.2-2 to Debian unstable, which wi
I should quickly mention that future workflow-related stuff in regards to
https://www.python.org/dev/peps/pep-0512 and the move to GitHub (e.g. CI),
happens on the core-workflow mailing list.
On Mon, 4 Jul 2016 at 15:35 Steve Dower wrote:
> On 04Jul2016 0822, Kevin Ollivier wrote:
> > On 7/4/16,
On 04Jul2016 0822, Kevin Ollivier wrote:
On 7/4/16, 3:32 AM, "Python-Dev on behalf of Sven R. Kunze"
wrote:
If you need some assistance here, let me know.
I also offer my help with setting up CI and automated builds. :) I've actually
done build automation for a number of the projects I've
On 03.07.2016 06:09, Nick Coghlan wrote:
> On 2 July 2016 at 16:17, Ludovic Gasc wrote:
>> Hi everybody,
>>
>> I fully understand that AsyncIO is a drop in the ocean of CPython, you're
>> working to prepare the entire 3.5.3 release for December, not yet ready.
>> However, you might create a 3.5.2.
On 7/4/16, 3:32 AM, "Python-Dev on behalf of Sven R. Kunze"
wrote:
>On 03.07.2016 16:39, Guido van Rossum wrote:
>> Another thought recently occurred to me. Do releases really have to be
>> such big productions? A recent ACM article by Tom Limoncelli[1]
>> reminded me that we're doing relea
On 03.07.2016 16:39, Guido van Rossum wrote:
Another thought recently occurred to me. Do releases really have to be
such big productions? A recent ACM article by Tom Limoncelli[1]
reminded me that we're doing releases the old-fashioned way --
infrequently, and with lots of manual labor. Maybe we
s.
Probably no better opportunity to make such a fundamental change as we move to
a new VCS...
Cheers,
Steve
Top-posted from my Windows Phone
-Original Message-
From: "Guido van Rossum"
Sent: 7/3/2016 7:42
To: "Python-Dev"
Cc: "Nick Coghlan"
Subject: Re: [
Another thought recently occurred to me. Do releases really have to be
such big productions? A recent ACM article by Tom Limoncelli[1]
reminded me that we're doing releases the old-fashioned way --
infrequently, and with lots of manual labor. Maybe we could
(eventually) try to strive for a lighter-
Hi Nick,
First, thanks a lot for your detailed answer, it was very instructive to me.
My answers below.
2016-07-03 6:09 GMT+02:00 Nick Coghlan :
> On 2 July 2016 at 16:17, Ludovic Gasc wrote:
> > Hi everybody,
> >
> > I fully understand that AsyncIO is a drop in the ocean of CPython, you're
> >
On 2 July 2016 at 16:17, Ludovic Gasc wrote:
> Hi everybody,
>
> I fully understand that AsyncIO is a drop in the ocean of CPython, you're
> working to prepare the entire 3.5.3 release for December, not yet ready.
> However, you might create a 3.5.2.1 release with only this AsyncIO fix ?
That wou
Hi everybody,
I fully understand that AsyncIO is a drop in the ocean of CPython, you're
working to prepare the entire 3.5.3 release for December, not yet ready.
However, you might create a 3.5.2.1 release with only this AsyncIO fix ?
PEP 440 doesn't seem to forbid that even if I see only 3 digits
On 06/28/2016 02:51 PM, Larry Hastings wrote:
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?
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
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
17 matches
Mail list logo
