Hello Łukasz,
I consider this one critical enough to get into 3.8:
https://bugs.python.org/issue38319
Long story short: shutil.copyfile() and socket.sendfile() are broken on
32-bit platforms for files >= 2GiB.
shutil.copyfile() was modified by me in the 3.8 cycle so the bug only
affects 3.8 and 3.9
The steering council also proposes that no changes be made to PEP 13 between
Nov 1 and Dec 15.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/m
Hi folks -
Per PEP 13, a new Steering Council will be voted in after each feature
release. As Victor has pointed out, 3.8 is scheduled for 2019-10-21 so we
should start talking about the election.
The Steering Council discussed this and the timeline proposed for the vote
is as follows:
* The nom
On 9/30/2019 3:48 AM, Łukasz Langa wrote:
To help our chances, please avoid any source-related activity on the 3.8
branch from now until the release of 3.8.0. Yes, that also counts for
bug fixes unless they are critical. (Yeah, it might be a bit annoying
but nobody wants to be the person who i
> On 30 Sep 2019, at 16:09, Nick Coghlan wrote:
>
> I've filed https://bugs.python.org/issue38326 as a release blocker, as
> I don't think we should be cutting RCs when changes have been made to
> a PEP-approved API without any pre-merge design discussion.
Nick, Victor, as co-authors of said PE
On Mon, 30 Sep 2019 at 17:48, Łukasz Langa wrote:
>
> Team,
> amazing job on getting us back on track over the weekend.
>
> Thank you
> All release blockers and deferred release blockers solved. And there was
> relatively little additional activity on the branch -- as expected at this
> point! T
Team,
amazing job on getting us back on track over the weekend.
Thank you
All release blockers and deferred release blockers solved. And there was
relatively little additional activity on the branch -- as expected at this
point! Thank you for this, it will help get the release candidate out on t
