python-committers October 2019

python-committers@python.org

15 participants
14 discussions

Steering Council Nomination Period - Begins Nov 1

by Ewa Jodlowska

Hi everyone, The nomination period for the next steering council vote will begin November 1 AoE* and will end November 15 AoE*. Open: 2019-11-01 00:00:00 AoE (2019-11-01 08:00:00 EDT) Close: 2019-11-16 00:00:00 AoE (2019-11-16 07:00:00 EDT) On November 1, the Discourse category for nominations ( https://discuss.python.org/c/users/steering-council-nominations) will open for posting. Core developers: please be sure to check your email address in https://github.com/python/voters/blob/master/python-core.toml to ensure you are listed with your desired email address set in the voting_address field. This is where ballots will be sent to eligible voters when the vote begins. Please note that this has changed, previously a .voters.csv file held these overrides. Voting begins December 1st and ends December 15th. Thanks, Ewa * https://www.timeanddate.com/time/zones/aoe

1 year, 8 months

What it's like being on the steering council

by Brett Cannon

In case people are thinking about nominations next month and wanted to know what it's like and the time commitment involved, I wrote a blog post on the subject at https://snarky.ca/what-its-like-to-be-on-the-python-steering-council/.

1 year, 8 months

[WARNING] Some users who downloaded the Python 3.5.8 .xz tarball got the wrong version

by Larry Hastings

Due to awkward CDN caching, some users who downloaded the source code tarballs of Python 3.5.8 got a preliminary version instead of the final version. As best as we can tell, this only affects the .xz release; there are no known instances of users downloading an incorrect version of the .tgz file. If you downloaded "Python-3.5.8.tar.xz" during the first twelve hours of its release, you might be affected. It's easy to determine this for yourself. The file size (15,382,140 bytes) and MD5 checksum (4464517ed6044bca4fc78ea9ed086c36) published on the release page have always matched the correct version. Also, the GPG signature file will only report a "Good signature" for the correct .xz file (using "gpg --verify"). What's the difference between the two? The only difference is that the final version also merges a fix for Python issue tracker #38243: https://bugs.python.org/issue38243 The fix adds a call to "html.escape" at a judicious spot, line 896 in Lib/xmlrpc/server.py. The only other changes are one new test, to ensure this new code is working, and an entry in the NEWS file. You can see the complete list of changes here: https://github.com/python/cpython/pull/16516/files What should you do? It's up to you. * If you and your users aren't using the XMLRPC library built in to Python, you don't need to worry about which version of 3.5.8 you downloaded. * If you downloaded the .tgz tarball or the Git repo, you already have the correct version. * If you downloaded the xz file and want to make sure you have the fix, check the MD5 sum, and if it's wrong download a fresh copy (and make sure that one matches the known good MD5 sum!). To smooth over this whole sordid mess, I plan to make a 3.5.9 release in the next day or so. It'll be identical to the 3.5.8 release; its only purpose is to ensure that all users have the same updated source code, including the fix for #38243. Sorry for the mess, everybody, //arry/

1 year, 9 months

[RELEASED] Python 3.5.8 is (finally) released

by Larry Hastings

On behalf of the Python development community, I'm relieved to announce the availability of Python 3.5.8. 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.8 here: https://www.python.org/downloads/release/python-358/ Oh what fun, //arry/

1 year, 9 months

PEP 13 and approval voting.

by Thomas Wouters

For those who don't check discourse regularly, I've posted a suggested change to PEP 13, switching it to approval voting: https://discuss.python.org/t/amendment-to-pep-13-to-allow-approval-voting/2…. Discussion should preferably happen on discourse, but I'll happily take feedback directly, as well. I'll add an official vote to the discourse topic in a few days, and it'll run for two weeks, as required by PEP 13. -- Thomas Wouters <thomas(a)python.org> Hi! I'm an email virus! Think twice before sending your email to help me spread!

1 year, 9 months

[RELEASE] Python 3.8.0 is now available

by Łukasz Langa

On behalf of the Python development community and the Python 3.8 release team, I’m pleased to announce the availability of Python 3.8.0. Python 3.8.0 is the newest feature release of the Python language, and it contains many new features and optimizations. You can find Python 3.8.0 here: https://www.python.org/downloads/release/python-380/ <https://www.python.org/downloads/release/python-380/> Most third-party distributors of Python should be making 3.8.0 packages available soon. 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 follow at regular bi-monthly intervals starting in December of 2019. 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. https://www.python.org/psf/ <https://www.python.org/psf/> - Ł

1 year, 9 months

[RELEASE] Python 3.7.5 is now available

by Ned Deily

Python 3.7.5 is now available, the next maintenance release of Python 3.7. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-375/ Note that the next feature release of Python 3, Python 3.8.0, is also now available. Python 3.8 contains many new features and optimizations. You should consider upgrading to it. We plan to continue regular bugfix releases of Python 3.7.x through mid-year 2020 and provide security fixes for it until mid-year 2023. More details are available in PEP 537, the Python 3.7 Release Schedule (https://www.python.org/dev/peps/pep-0537/). 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. -- Ned Deily nad(a)python.org -- []

1 year, 9 months

I'm working on the release of Python 3.8.0 right now

by Łukasz Langa

Please hold your breath. Unless you have some last minute blocker, then let me know immediately. - Ł

1 year, 9 months

Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues

by Raymond Hettinger

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

1 year, 9 months

[RELEASED] Python 3.5.8rc1 is released

by Larry Hastings

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 year, 9 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers October 2019