Mailman 3 June 2020 - python-committers

Please welcome Lysandros Nikolaou to the team!
by Brett Cannon 30 Jun '20

30 Jun '20

<eom>

8 7

[RELEASE] Python 3.8.4rc1 is now ready for testing
by Łukasz Langa 30 Jun '20

30 Jun '20

Python 3.8.4rc1 is the release candidate of the fourth maintenance release of Python 3.8. Go get it here: https://www.python.org/downloads/release/python-384rc1/ <https://www.python.org/downloads/release/python-384rc1/> Assuming no critical problems are found prior to 2020-07-13, the scheduled release date for 3.8.4, 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 and as such its main purpose is testing. Maintenance releases for the 3.8 series will continue at regular bi-monthly intervals, with 3.8.5 planned for mid-September 2020. What’s new? The Python 3.8 series is the newest feature release of the Python language, and it contains many new features and optimizations. 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. This is the first bugfix release that is considerably smaller than the previous three. There’s 20% less changes at 130 commits than the average of previous three releases. Detailed information about all changes made in version 3.8.4 specifically can be found in its change log <https://docs.python.org/release/3.8.4rc1/whatsnew/changelog.html#python-3-8…>. 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. Your friendly release team, Ned Deily @nad <https://discuss.python.org/u/nad> Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower> Łukasz Langa @ambv <https://discuss.python.org/u/ambv>

1 0

[RELEASE] Python 3.7.8 and 3.6.11 now available - last 3.7.x bugfix release
by Ned Deily 28 Jun '20

28 Jun '20

https://discuss.python.org/t/python-3-7-8-and-3-6-11-now-available-last-3-7… -- Ned Deily nad(a)python.org -- []

1 0

[RELEASE] Python 3.7.8rc1 and 3.6.11rc1 are now available for testing
by Ned Deily 17 Jun '20

17 Jun '20

Details here: https://discuss.python.org/t/python-3-7-8rc1-and-3-6-11rc1-are-now-availabl… https://www.python.org/downloads/release/python-378rc1/ https://www.python.org/downloads/release/python-3611rc1/ -- Ned Deily nad(a)python.org -- []

1 0

Vote to promote Lysandros Nikolaou
by Pablo Galindo Salgado 15 Jun '20

15 Jun '20

Hi everyone, Guido and I have opened a poll to promote Lysandros Nikolaou as a core developer. Please read more and vote here: https://discuss.python.org/t/vote-to-promote-lysandros-nikolaou/4445 Thank you! Regards from cloudy London, Pablo Galindo Salgado

1 0

Final reminder: 3.7.8 / 3.6.11 cutoff Monday, last non-security bugfixes for 3.7.x
by Ned Deily 12 Jun '20

12 Jun '20

We will be accecpting commits to the 3.7 branch until this coming Monday 06-15 23:59 AOE. At that time, 3.7 will effectively enter security-fix mode. That will also be the deadline for any additional security-fixes for release in 3.6.11. Release candidates will follow shortly thereafter. Assuming no release-blocker issues arise during the release candidate testing, 3.7.8 and 3.6.11 will release on 06-27. https://discuss.python.org/t/upcoming-cutoffs-for-3-9-3-8-3-7-and-3-6-relea… -- Ned Deily nad(a)python.org -- []

1 0

[RELEASE] Python 3.9.0b3 is now available for testing
by Łukasz Langa 09 Jun '20

09 Jun '20

On behalf of the entire Python development community, and the currently serving Python release team in particular, I’m pleased to announce the release of Python 3.9.0b3. Get it here: https://www.python.org/downloads/release/python-390b3/ <https://www.python.org/downloads/release/python-390b3/> Wait, Beta 3? What happened to Beta 2? Beta 2? Speak of him no more. We disappeared him. He was a bad release. Truly awful. I get shivers just thinking about it. Never mention that name again in this house. I mean, long story short, in Beta 2 you couldn’t do urllib.request.urlopen("https://www.python.org").read() because it wouldn’t find root certificates due to a bug <https://bugs.python.org/issue40924>. Since this was a problem only apparent on an installed Python, it wasn’t identified by unit tests and was only found by Ned while he was testing his Mac installer. By the time we learned of the severity of the bug I already tagged and published the release on python.org <http://python.org/>. That’s why we couldn’t just re-do the release under the same version. Sorry for the trouble. We’re tweaking our release process to catch this problem sooner in future releases. Now, back to regular programming… This is a beta preview of Python 3.9 Python 3.9 is still in development. This release, 3.9.0b3, is the third of five planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. Call to action We strongly encourage maintainers of third-party Python projects to test with 3.9 during the beta phase and report issues found to the Python bug tracker <https://bugs.python.org/> as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2020-08-10). Our goal is have no ABI changes after beta 5 and as few code changes as possible after 3.9.0rc1, the first release candidate. To achieve that, it will be extremely important to get as much exposure for 3.9 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments. Major new features of the 3.9 series, compared to 3.8 Some of the new major new features and changes in Python 3.9 are: PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In Standard Collections PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and variable annotations PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable annual release cadence PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove prefixes and suffixes PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not block on resurrected objects; BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows process management without races and signals; BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to version 13.0.0; BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized multiple times in the same process, it does not leak memory anymore; A number of Python builtins (range, tuple, set, frozenset, list, dict) are now sped up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall; A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, _functools, _json, _locale, operator, resource, time, _weakref) now use multiphase initialization as defined by PEP 489 <https://www.python.org/dev/peps/pep-0489/>; A number of standard library modules (audioop, ast, grp, _hashlib, pwd, _posixsubprocess, random, select, struct, termios, zlib) are now using the stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>. (Hey, fellow core developer, if a feature you find important is missing from this list, let Łukasz know <mailto:lukasz@python.org>.) The next pre-release, the fourth beta release of Python 3.9, will be 3.9.0b4. It is currently scheduled for 2020-06-29. More resources Online Documentation <https://docs.python.org/3.9/> PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule Report bugs at https://bugs.python.org <https://bugs.python.org/>. Help fund Python and its community <https://discuss.python.org/psf/donations/>. Your friendly release team, Ned Deily @nad <https://discuss.python.org/u/nad> Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower> Łukasz Langa @ambv <https://discuss.python.org/u/ambv>

1 0

Recent changes on the CI jobs run on pull requests
by Victor Stinner 09 Jun '20

09 Jun '20

Hi, Changes on CIs run on GitHub pull requests: * Travis CI became mandatory * Azure Pipelines is no longer mandatory * Please watch Windows x64 job: I would like to make it mandatory in 2 weeks -- I asked to make Azure Pipelines CI not mandatory on Python PRs since there were more and more random failures and no one was available to investigate. Also, sadly, currently Azure Pipelines has no way to only re-trigger a single failed job, but requires to close/re-open a PR to schedule all jobs. Sadly, some Python tests fail randomly and so sometimes another CI fails. Also, for backport PRs, closing a PR triggers miss-inlington which removes the branch which prevents to re-open the PR. A new backport PR must be created which is not convenient. Until Azure Pipelines issues are fixed, I asked Mariatta to make Travis CI mandatory. In fact, I expected Travis CI to be mandatory, I never noticed that it was optional. I didn't know that only Azure Pipelines was mandatory! -- I also asked Mariatta to make the GitHub Action ("GHA") Windows x64 job mandatory. GHA workflow jobs are skipped for "documentation only" changes, to not waste CI resources. GHA configuration used "paths-ignored". Sadly (again!?), if a job using "paths-ignored" is mandatory, a PR cannot be merged because the mandatory job is skipped and will never be run... Sadly, it even seems to be a known GitHub issue which is not going to be fixed soon! I removed "paths-ignored" to always run jobs, to be able to make a job mandatory. Then Filipe Laíns found a way to add a new quick (around 15 seconds!) job just for check if a change is documentation only: the job result is then used to decide if build jobs must be skipped. In short, the behavior is the same than previously: GHA build jobs are skipped on documentation only changes. The main difference is that it became possible to make a GHA job mandatory. I backported the GHA workflow configuration to Python 3.8 and 3.7. Mariatta suggested to watch the Windows x64 job for 2 weeks to check if it's stable before making it mandatory. Hopefully, in my experience, the Windows x64 job is (very) reliable. -- By the way, the GHA macOS job fails randomly, I have no idea why. For example, I saw the job being cancelled after 5 minutes for an unknown reason. I read that a job can be cancelled if "fail fast" is used and another job fails. It doesn't seem like we use "fail fast" and others jobs passed successfully. -- Links to CI changes. Make Azure Pipelines optional on GitHub PRs: https://bugs.python.org/issue39837 Always run GitHub action jobs, even on documentation-only jobs: https://bugs.python.org/issue40548 Make one Windows CI job mandatory: https://discuss.python.org/t/make-one-windows-ci-job-mandatory/4047 Make Travis CI (and Windows x64 ?) mandatory: https://github.com/python/core-workflow/issues/365 Make Windows (x64) GitHub action mandatory on master branch: https://github.com/python/core-workflow/issues/368 -- It's so hard to get a bunch of reliable CIs on many platforms (Linux, Windows, macOS) and minimize the failure rate :-( Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 1

Upcoming cutoffs for 3.9, 3.8, 3.7, and 3.6 releases! Last chance for 3.7 bugfixes!
by Ned Deily 06 Jun '20

06 Jun '20

https://discuss.python.org/t/upcoming-cutoffs-for-3-9-3-8-3-7-and-3-6-relea… -- Ned Deily nad(a)python.org -- []

1 0