python-committers February 2019

python-committers@python.org

30 participants
23 discussions

GitHub: remove the "needs backport to 3.5" label?

by Victor Stinner

Hi, Python 3.5 entered security fix only mode. Should we now remove the "needs backport to 3.5" label? Other security only branches don't have this label neither (3.3 and 3.4). Victor

1 year, 8 months

2019 Steering Council Election Results

by Ernest W. Durbin III

Voting closed at 2019-02-04 12:00 UTC as prescribed in [PEP 8100](https://www.python.org/dev/peps/pep-8100/). Of 96 eligible voters, 69 cast ballots. The top five vote-getters are: - Barry Warsaw - Brett Cannon - Carol Willing - Guido van Rossum - Nick Coghlan No conflict of interest as defined in PEP 13 were observed. Eligible voters have received result notification emails from helios, and may return to the system to audit/verify the results. Thanks to all participants! It was an honor serving as the administrator for the governance votes. -Ernest W. Durbin III

2 years, 2 months

OpenMandriva and Fedora abandoned Discourse for development discussions

by Victor Stinner

Hi, Follow-up of the previous "Can we choose between mailing list and discuss.python.org?" thread. Python isn't the first project who "experimented" Discourse to replace mailing lists. It seems like Fedora and OpenMandriva are coming back to mailing lists, at least for "development discussions": https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedorap… Fedora uses Mailman 3: https://lists.fedoraproject.org/archives/ and Discourse: https://discussion.fedoraproject.org/ Victor who is more and more confused by these topics... -- Night gathers, and now my watch begins. It shall not end until my death.

2 years, 2 months

Proposed dates for Python 3.4.10 and Python 3.5.7

by Larry Hastings

Howdy howdy! It's time to make the next bugfix release of 3.5--and the /final/ release /ever/ of Python 3.4. Here's the schedule I propose: 3.4.10rc1 and 3.5.7rc1 - Saturday March 2 2019 3.4.10 final and 3.5.7 final - Saturday March 16 2019 What's going in these releases? Not much. I have two outstanding PRs against 3.5: bpo-33127 GH-10994: Compatibility patch for LibreSSL 2.7.0 bpo-34623 GH-9933: XML_SetHashSalt in _elementtree and one PR against 3.4: bpo-34623 GH-9953: Use XML_SetHashSalt in _elementtree I expect to merge all three of those, I just need to get around to it. There's one more recent security fix (bpo-35746, GH-11569) that I want in these releases that still needs backporting. And that's the entire list. bpo-34623 is the only current release blocker for either 3.4 or 3.5--I'm not aware of anything else in the pipeline. If you have anything you think needs to go into the next 3.5, or the final 3.4, and it's /not/ listed above, please either file a GitHub PR, file a release-blocker bug on bpo, or email me directly. Good night sweet Python 3.4, and flights of angels sing thee to thy rest! //arry/

2 years, 2 months

Announcing: signups are open for the 2019 Python Language Summit

by Łukasz Langa

The Python Language Summit is an event for the developers of Python implementations (CPython, PyPy, Jython, and so on) to share information, discuss our shared problems, and — hopefully — solve them. These issues might be related to the language itself, the standard library, the development process, status of Python 3.8 (or plans for 3.9), the documentation, packaging, the website, et cetera. The Summit focuses on discussion more than on presentations. If you’d like to attend **and actively participate** in the discussions during the Language Summit, please fill in this form by March 21st 2019: https://goo.gl/forms/pexfOGDjpV0BWMer2 We will be evaluating all applications and confirm your attendance by April 15th. Note: **your attendance is not confirmed** until you heard back from us. You don't need to be registered for PyCon in order to attend the summit. One of the goals of the Language Summit is to speed up the discussions and decision making process. Communication over Discourse (or mailing lists!) is generally more time consuming. As part of efforts to make this event more open and less mysterious, we are not requiring invitations by core developers anymore. However, please understand that we will have to be selective as space and time are limited. In particular, we are prioritizing active core contributors, as well as those who we believe will be able to improve the quality of the discussions at the event and bring a more diverse perspective to core Python developers. As for other changes this year, A. Jesse Jiryu Davis will be covering the event and will post a detailed write up on the official blog of the PSF shortly after the conference. We hope to see you at the Summit! - Mariatta and Łukasz PS. If you have any questions, the Users section of our Discourse instance (https://discuss.python.org/c/users) is the best place to ask. For private communication, write to mariatta(a)python.org and/or lukasz(a)python.org.

2 years, 2 months

[RELEASE] Python 3.8.0a1 is now available for testing

by Łukasz Langa

I packaged another release. Go get it here: https://www.python.org/downloads/release/python-380a2/ Python 3.8.0a2 is the second of four planned alpha releases of Python 3.8, the next feature release of Python. During the alpha phase, Python 3.8 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. The next preview release, 3.8.0a3, is planned for 2019-03-25. This time around the stable buildbots were a bit less green than they should have. This early in the cycle, I didn't postpone the release and I didn't use the revert hammer. But soon enough, I will. Let's make sure future changes keep the buildbots happy. - Ł

2 years, 2 months

Andrés Delfino got the bug triage permission

by Victor Stinner

Hi, As Serhiy Storchaka noticed, Andrés Delfino is very active in Python since April 2018. He got not less than 79 commits merged into mater: https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Aa… $ git log --author=adelfino(a)gmail.com|grep ^commit -c 79 Andrés Delfino enhanced a lot the documentation, but also stdlib modules: --- commit b2043bbe6034b53f5ad337887f4741b74b70b00d Author: Andrés Delfino <adelfino(a)gmail.com> Date: Sat May 5 13:07:32 2018 -0300 bpo-33422: Fix quotation marks getting deleted when looking up byte/string literals on pydoc. (GH-6701) commit c3b7a6dfb9c7e69093c9fe78ab587e14743e5152 Author: Andrés Delfino <adelfino(a)gmail.com> Date: Mon Apr 30 13:30:53 2018 -0300 bpo-33352: Skip test_regrtest test if rt.bat does not exist (GH-6654) commit a6dc531063efe3a8d47ff4639729060c72a3688c Author: Andrés Delfino <adelfino(a)gmail.com> Date: Fri Oct 26 11:56:57 2018 -0300 bpo-34789: make xml.sax.make_parser accept iterables of all types (GH-9576) --- I decided to give him the bug triage permission. I sent Andrés instructions how to triage bug and links into the devguide. I asked him to ask me before closing a bug. Congrats Andrés ;-) Victor -- Night gathers, and now my watch begins. It shall not end until my death.

2 years, 2 months

Re: [python-committers] Date for the Language Summit?

by Mariatta

Date is listed here. More info will be added here too. https://us.pycon.org/2019/events/language-summit/ Process will be slightly different this year. Sorry, I'm busy with PyCascades this week. Next time I'll have more time to devote to this. On Thu, Feb 21, 2019, 5:21 AM Mariatta <mariatta.wijaya(a)gmail.com> wrote: > Date is listed here. More info will be added here too. > https://us.pycon.org/2019/events/language-summit/ > Process will be slightly different this year. Sorry, I'm busy with > PyCascades this week. Next time I'll have more time to devote to this. > > On Thu, Feb 21, 2019, 2:45 AM Matthias Klose <doko(a)ubuntu.com> wrote: > >> On 21.02.19 11:38, Victor Stinner wrote: >> > Hi, >> > >> > What will be the date of the Language Summit? I had to organize myself >> > very soon to get cheap flight and hotel, so I already booked >> > everything for Pycon US :-) >> >> +1 >> >> > Who will be allowed to attend? Will we have enough seats for all >> > CPython core devs? >> > >> > Mariatta, Lukasz: do you plan to invite people from other popular >> > Python projects or other Python implementations? >> >> I would like to see some presence of setuptools/pip maintainers. I think >> that >> was missed at last PyCon by Conda developers, and distro packagers from >> RedHat >> and Debian/Ubuntu. >> >> Matthias >> _______________________________________________ >> python-committers mailing list >> python-committers(a)python.org >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> >

2 years, 2 months

Date for the Language Summit?

by Victor Stinner

Hi, What will be the date of the Language Summit? I had to organize myself very soon to get cheap flight and hotel, so I already booked everything for Pycon US :-) Who will be allowed to attend? Will we have enough seats for all CPython core devs? Mariatta, Lukasz: do you plan to invite people from other popular Python projects or other Python implementations? Victor -- Night gathers, and now my watch begins. It shall not end until my death.

2 years, 2 months

New core developers

by Serhiy Storchaka

What do you think about making Zackery Spytz, Andre Delfino and Alexey Izbyshev core developers? Zackery Spytz contributed a lot of bugfixes, mostly for reference leaks and possible crashes. Some of them are trivial (but hard to discover), others are nontrivial, but all are qualified. https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3AZ… Andre Delfino contributed an enormous number of docfixes. https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Aa… Alexey Izbyshev is not so active as the above two monsters, but his code and comments on the bug tracker look qualified. https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Ai… Could anybody please ask them whether they want to be core developers? I afraid that I may not have time for this, and in any case my English is not good. You have my voice for all of them. I think they could be core developers months ago, but I waited for the end of the Steering Council election.

2 years, 2 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers February 2019