Please participate on
to cast a vote.
The poll's text is copied below:
I (Andrew Svetlov) want to promote Karthikeyan, a developer from
India, to the Python Core Developers list.
I'm mentoring *Karthikeyan* starting from this spring. He [got
on https://bugs.python.org since September of 2018, and he is very
active on the bug tracker.
He has about [100 Pull
80+ were merged already; 5 PRs are waiting for review currently.
The main interest are of Karthikeyan is `unittest.mock` library, he
helped a lot to add async mock in Python 3.8; he helped me in my work
on asyncio issues.
Also, Karthikeyan is very strong in reviews, both in formal text
part and manual checking that the proposed change is actually working
fine. There are about 400 Pull Requests where Karthikeyan was a
reviewer in very different areas of the Stadard Python Library.
As a triager, he took a part in 125+ discussions on the bug tracker
issues; I personally very appreciate this work.
Karthikeyan had participated in Core Developers Spring in London this
year, some of you had a chance to meet him in person doring the event.
Last but not least, Karthikeyan recently received "Google Open Source
Peer Bonus" award for his contributions to CPython.
I offer to mentor Karthikeyan for a month once he would become a core
dev to help him with understanding our workflow and etc.
The vote is starting now and will be finished in a week as PEP 13 states:
> … It is granted by receiving at least two-thirds positive votes in a core team vote that is open for one week and with no veto by the steering council."
**Upd** Added a poll widget
*This is a reminder that voting will end December 16, 2019 12:00 UTC.*
If you have not yet voted, please do so soon. Momentarily, Ernest will
resend all the ballots to those that have not voted yet. If you cannot find
your ballot, try searching spam for system(a)heliosvoting.org.
If you run into any issues, please email myself (ewa(a)python.org) and Ernest
Python 3.8.1rc1 is the release candidate of the first maintenance release of Python 3.8.
The Python 3.8 series is the newest feature release of the Python language, and it contains many new features and optimizations. You can find Python 3.8.1rc1 here:
Assuming no critical problems are found prior to 2019-12-16, the scheduled release date for 3.8.1 as well as Ned Deily's birthday, no code changes are planned between this release candidate and the final release.
That being said, please keep in mind that this is a pre-release of 3.8.1 and as such its main purpose is testing.
See the “What’s New in Python 3.8 <https://docs.python.org/3.8/whatsnew/3.8.html>” document for more information about features included in the 3.8 series. Detailed information about all changes made in 3.8.0 can be found in its change log.
Maintenance releases for the 3.8 series will continue at regular bi-monthly intervals, with 3.8.2 planned for February 2020.
We hope you enjoy Python 3.8!
Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.
My name is Lars Gustäbel. I am the author of the tarfile module, and I have
been its maintainer for over ten years. I have not been active in the
bugtracker for a long time now, and I don't see that this will change in the
future. There are many open bugs and issues that need attention, and I am sure
that many people are dissatisfied with the current situation.
Therefore, I think it is best that I resign and someone else takes over as
maintainer of tarfile. It goes without saying that I will help with the switch
as well as I can.
It's that time for another reminder: code cutoffs for the last scheduled releases of 2019 are coming up soon. They are a little earlier than usual to try to avoid the end-of-December rush of various holidays. Łukasz will have more details forthcoming about **3.8.1rc1**. For the **3.7 branch**, the cutoff for **3.7.6rc1** is scheduled for this coming Monday (2019-12-09) by the end of day AOE. I have also now scheduled the cutoff for the next cumulative security source release for the **3.6 branch**, **3.6.10rc1**, for Monday as well. Please review open issues and ensure that any that you believe need to be addressed in any of these releases are either resolved or marked as a **release blocker**. Any assistance you can provide in helping resolve issues will be greatly appreciated. As usual, following the rc1 cutoff, changes merged to the 3.7 branch will be released in **3.7.7** three months from now unless you mark the issue as a release blocker prior to **3.7.6 final**, planned for release on **2019-12-16**, and explain why the change should be cherry-picked into the final release. And as always, any proposed changes for the 3.6 branch need to meet the criteria for security branches and require release manager approval to merge.
Thanks for your continued efforts!
3.8 release PEP: https://www.python.org/dev/peps/pep-0569/
3.7 release PEP: https://www.python.org/dev/peps/pep-0537/
3.6 release PEP: https://www.python.org/dev/peps/pep-0494/
Security branch criteria: https://devguide.python.org/devcycle/#security-branches
nad(a)python.org --