python-committers September 2019

python-committers@python.org

20 participants
16 discussions

Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues
by Raymond Hettinger 13 Oct '19

13 Oct '19

Another essential bit of tooling for the migration: * Before filing a bug report or feature request, we ask people to search to see if there is already an issue in progress or a resolved issue on the topic. We need to make sure that on GitHub issues, people can still search our voluminous history of already evaluated and decided feature requests. Raymond

9 10

[RELEASED] Python 3.5.8rc1 is released
by Larry Hastings 12 Oct '19

12 Oct '19

On behalf of the Python development community, I'm chuffed to announce the availability of Python 3.5.8rc1. Python 3.5 is in "security fixes only" mode. This new version only contains security fixes, not conventional bug fixes, and it is a source-only release. You can find Python 3.5.8rc1 here: https://www.python.org/downloads/release/python-358rc1/ I think Python 3.5 may just barely outlive 2.7, //arry/

1 1

Currently working on the release of Python 3.8.0rc1
by Łukasz Langa 01 Oct '19

01 Oct '19

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 time. I'm working on cutting RC1 today Hopefully all sanity checks, as well as building the source tarball and the binary installers for macOS and Windows will all work out fine and we'll be seeing RC1 out tonight. RC2 and the date of 3.8.0 gold If we manage to avoid the need for RC2, we will be able to release 3.8.0 on October 14th. If we need an RC2, that will slip by a week. I hope we won't. Ideally RC1 should be identical codewise to 3.8.0. 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 introduced a last minute regression in a major release.) Note I didn't say I forbid any activity. I have no power over you, actually. More importantly though, I trust your judgement if you assess some bug is bad enough the fix absolutely has to get into 3.8.0. Moreover, I specifically said source-related activity because... 3.8.0 is important. To some users it will be the first and the last release in the 3.8 series they will see. We need you to focus on the docs now Are all your changes properly documented? Did you notice other changes you know of to have insufficient documentation? Can you help with the "What's New" document? anxiously configure-&&-makingly y'rs - Ł

5 7

Steering Council Election Timeline
by Ewa Jodlowska 30 Sep '19

30 Sep '19

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 nomination period will begin Nov 1, 2019 (do not post nominations until then) * Nomination period will end Nov 15, 2019 * Voting will begin Dec 1, 2019 * Voting will end Dec 15 Nominations will be collected via https://discuss.python.org/ (more details to follow). I will be handling all the email notifications related to the election and Ernest will continue to run the elections. I will send more information out in a couple of weeks. In the meantime, don't hesitate to reach out if you have any questions or concerns. Thank you, Ewa

2 1

3.7.5rc1 cutoff ahead
by Ned Deily 28 Sep '19

28 Sep '19

https://discuss.python.org/t/3-7-5rc1-cutoff-ahead/2288 A reminder: it is time for the next quarterly maintenance release of Python 3.7. The cutoff for **3.7.5rc1** is scheduled for this coming Monday (2019-09-16) by the end of day AOE. Please review open issues and ensure that any that you believe need to be addressed in 3.7.5 are either resolved or marked as a **release blocker**. Any assistance you can provide in helping resolve issues will be greatly appreciated. Following the rc1 cutoff, changes merged to the 3.7 branch will be released in 3.7.6 three months from now unless you mark the issue as a release blocker prior to **3.7.5 final**, planned for release on **2019-09-30** and explain why the change should be cherry-picked into the final release. Thanks to everyone who has been helping to ensure the continued success of Python 3.7! Our users truly appreciate it and are showing their confidence in us by the rapid adoption of these latest releases. P.S. A number of core developers are participating in this year's core developer sprint taking place this week in London. So it is a good time to catch many of us in the same place at the same time (and British Summer Time, at that). https://www.python.org/dev/peps/pep-0537/ -- Ned Deily nad(a)python.org -- []

1 2

ATTENTION: Python 3.8.0rc1 is due on Monday, Sep 30th
by Łukasz Langa 27 Sep '19

27 Sep '19

Hello fellow core developers and testers, as documented in PEP 569, we're less than 72 hours away from tagging the release candidate of Python 3.8.0. Ideally we'd only need one. Sadly, at the moment we're looking rather miserable release-blocker wise: https://bugs.python.org/issue?%40action=search&%40columns=activity&%40colum… <https://bugs.python.org/issue?@action=search&@columns=activity&@columns=id&…> The buildbots look better but they're also not perfect (there's too much red in recent history): https://buildbot.python.org/all/#/grid?branch=3.8&tag=stable <https://buildbot.python.org/all/#/grid?branch=3.8&tag=stable> If you're on any of the release blockers, please work on fixing them ASAP. If you're not on any release blockers, please avoid any commits to 3.8 for the time being. The release candidate should ideally *be* 3.8.0, we don't want any untested last-minute changes. Stabilizingly y'rs - Ł

1 0

Welcome Joannah Nanjekye to the team!
by Brett Cannon 25 Sep '19

25 Sep '19

While we wait for the last step of the infrastructure team to add Joannah to the Python Core team on GitHub, I wanted to welcome to the development team!

5 4

Python 3.8.0 final release and election of a new Steering Council?
by Victor Stinner 23 Sep '19

23 Sep '19

Hi, The PEP 13 says "A new council is elected after each feature release." Does it mean that we need elect a new Steering Council before/after Python 3.8.0 final release which is scheduled at 2019-10-21 (in more or less one month)? If a vote is organized, when should "Candidates advertise their interest in serving"? What will be the duration of the election phases and who will manage the vote? https://www.python.org/dev/peps/pep-0013/#electing-the-council Victor -- Night gathers, and now my watch begins. It shall not end until my death.

2 1

Timeline for 3.5.8
by Larry Hastings 19 Sep '19

19 Sep '19

Howdy howdy. Here's what I'm thinking for the next release of 3.5. This week I'm going to merge / reject all the outstanding PRs for 3.5, then cut rc1 at the Python Core Dev sprints next week, either Monday (2019/9/9) or Tuesday (2019/9/10). This isn't a lot of notice, but things have slowed down a lot for 3.5, so I suspect nobody's going to be inconvenienced or bothered by the short notice. However! If you /would/ be inconvenienced or bothered by the short notice--if you need more time to get a patch in for 3.5--just let me know and I can delay rc1. Assuming no problems crop up in rc1, 3.5.8 final will be released two weeks after 3.5.8 rc1. Cheers, //arry/

1 1

PEP 1: Relaxing the requirements for being a PEP sponsor
by Barry Warsaw 17 Sep '19

17 Sep '19

PEP 1 currently says that if a PEP is authored by a non-core developer, the author must find a core developer to sponsor their PEP. At today’s Steering Council meeting, we proposed to relax this requirement to allow non-core developers to sponsor a PEP with the approval of the Council. There is no change if the PEP author is a core developer; in that case the PEP still does not require a sponsor. Here is the PR with the proposed language change: https://github.com/python/peps/pull/1170 Feel free to weigh in on the PR. Cheers, -Barry

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers September 2019