Mailman 3 September 2021 - python-committers

Dates for the core dev sprints
by Brett Cannon 11 Oct '21

11 Oct '21

Based on the results of the poll on discuss.python.org, the core dev sprints will be from October 18 - 24. Based on feedback from last year and for simplicity reasons, the sprints will be hosted on the core dev Discord server (link in the Inquisition category on discuss.python.org to keep it private to core devs only; also don't forget to record your Discord username, which is formatted as r".+#\d+", to https://github.com/python/voters/ if you have not already). We currently have no organizer(s) for this, so right now this will be self-organized on the spot. 😅 If anyone wants to volunteer to run the sprints then please let the SC know.

4 4

What is github trying to tell me?
by Eric V. Smith 08 Sep '21

08 Sep '21

https://github.com/python/cpython/pull/28163 has two messages of: @ericvsmith <https://github.com/ericvsmith>: Status check is done, and it's a failure ❌ . Followed by the merge messages, followed by: @ericvsmith <https://github.com/ericvsmith>: Status check is done, and it's a success ✅ . What do the failure messages mean? Is it because I didn't wait for the checks to complete before merging? (It's a documentation only change that I previously committed to main without incident, so I didn't feel the need to wait for all of the checks to run before merging.) Thanks for any insight. Eric

5 6

[RELEASE] Python 3.10.0rc2 is available
by Pablo Galindo Salgado 07 Sep '21

07 Sep '21

Python 3.10 is one month away, can you believe it? This snake is still trying to bite as it has been an interesting day of fighting fires, release blockers, and a bunch of late bugs but your friendly release team always delivers :) You can get this new release while is still fresh here: https://www.python.org/downloads/release/python-3100rc2/ This is the second release candidate of Python 3.10 This release, **3.10.0rc2** , is the last preview before the final release of Python 3.10.0 on 2021-10-04. Entering the release candidate phase, only reviewed code changes which are clear bug fixes are allowed between release candidates and the final release. There will be no ABI changes from this point forward in the 3.10 series and the goal is that there will be as few code changes as possible. *The next release will be the final release of Python 3.10.0, which is currently scheduled for Monday, 2021-10-04.* Call to action ⚠️⚠️⚠️⚠️⚠️⚠️⚠️ *The 3.10 branch is now accepting changes for 3.10.**1*. To maximize stability, the final release will be cut from the v3.10.0rc2 tag. If you need the release manager (me) to cherry-pick any critical fixes, mark issues as release blockers, and/or add me as a reviewer on a critical backport PR on GitHub. To see which changes are currently cherry-picked for inclusion in 3.10.0, look at the short-lived branch-v3.10.0 https://github.com/python/cpython/tree/branch-v3.10.0 on GitHub. ⚠️⚠️⚠️⚠️⚠️⚠️⚠️ *Core developers: all eyes on the docs now* - Are all your changes properly documented? - Did you notice other changes you know of to have insufficient documentation? *Community members* We strongly encourage maintainers of third-party Python projects to prepare their projects for 3.10 compatibilities during this phase. As always, report any issues to [the Python bug tracker ](https://bugs.python.org/). Please keep in mind that this is a preview release and its use is **not** recommended for production environments. And now for something completely different Maxwell's demon is a thought experiment that would hypothetically violate the second law of thermodynamics. It was proposed by the physicist James Clerk Maxwell in 1867. In the thought experiment, a demon controls a small massless door between two chambers of gas. As individual gas molecules (or atoms) approach the door, the demon quickly opens and closes the door to allow only fast-moving molecules to pass through in one direction, and only slow-moving molecules to pass through in the other. Because the kinetic temperature of a gas depends on the velocities of its constituent molecules, the demon's actions cause one chamber to warm up and the other to cool down. This would decrease the total entropy of the two gases, without applying any work, thereby violating the second law of thermodynamics. We hope you enjoy those new releases! 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. Regards from a plane going to Malaga, Your friendly release team, Pablo Galindo @pablogsal Ned Deily @nad Steve Dower @steve.dower

1 0

[RELEASE] Python 3.7.12 and 3.6.15 security updates now available
by nad＠python.org 06 Sep '21

06 Sep '21

The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.

2 1

New Python Triagers: Andrei Kulakov and Yurii Karabas
by Ken Jin 06 Sep '21

06 Sep '21

Hi everyone, Last week we added two new members to the Python triage team: Andrei Kulakov and Yurii Karabas. [1] Andrei (andrei.avk on bpo and akulakov on GitHub) has been extremely active on the bug tracker. He's helped out in a wide range of issues by providing useful explanations, suggestions and PRs. I appreciate him helping us move issues forward. [2] Yurii (uriyyo <https://bugs.python.org/user34361> on bpo and on GitHub) has worked on various parts of asyncio, typing and parts of the compiler. I appreciate his help in clearing our issue backlog for the typing module. I'm happy to mentor their triage activities for one month (or more if required). Congrats Andrei and Yurii! [1] https://github.com/python/core-workflow/issues/414 [2] https://github.com/python/core-workflow/issues/413

1 0

Deprecation policy reminder
by Łukasz Langa 02 Sep '21

02 Sep '21

Hi there, I noticed some deprecation activity this week. Nice! I'd just like to remind everyone that we have a policy for that described in PEP 387 <https://www.python.org/dev/peps/pep-0387/> It's a very short PEP so I recommend you read it in its entirety. The important piece I want to highlight is that we cannot deprecate a feature in one release and remove it in the next one. We need at least two releases with the warning. Relevant quotes: > Python's yearly release process (PEP 602 <https://www.python.org/dev/peps/pep-0602>) means that the deprecation period must last at least two years. and: > Wait for the warning to appear in at least two minor Python versions of the same major version, or one minor version in an older major version (e.g. for a warning in Python 3.10, you either wait until at least Python 3.12 or Python 4.0 to make the change). It's fine to wait more than two releases. Since this PEP is easy to miss, I linked it to the docs of DeprecationWarning in GH-28123 <https://github.com/python/cpython/pull/28123>. Cheers, Ł

4 4