Mailman 3 May 2021 - Python-Dev

Python release timeline plot
by Michał Górny May 2, 2021

May 2, 2021

Hi, I've been working on visualizing some data on Python in Gentoo, and made a timeline of Python releases as a side result. I've figured some of you might be interested, so I've decided to share it. The result: https://mgorny.pl/python-timeline.html Script: https://github.com/mgorny/gpyutils/blob/master/timeline.py Data: https://github.com/mgorny/gpyutils/blob/master/timeline.toml I've (roughly) covered the versions between 2.5 and 3.10 (2.5 is the oldest I've seen during my time in Gentoo, also the timeline's gotten narrow already). dev covers the period between start of development and first alpha. alpha goes from a1 to b1, beta from b1 to rc1, rc from rc1 to final. stable goes to the last bugfix release, and security from that until the last security release. A few notes: 1. The data is cut off to the right, and for technical reasons this means tooltips will display early end dates. 2. The right-most data is based on approximate dates where schedules aren't precise, esp. 3.10 assumes 'approximately 18 months' for stable status. 3. Start of development is only mentioned in the newest schedules. For older versions, I've took the data of the commit changing PYTHON_VERSION in configure.{ac,in} (which seems to match start of development in newer schedules). 4. Where data on last bugfix release wasn't available in schedules, I've looked through release notes. 5. I've deliberately skipped dev period for 2.5 not to overstretch it to the left. If you see any mistakes, please let me know. -- Best regards, Michał Górny

1 0

Re: Announcing the CPython Docs Workgroup
by Raymond Hettinger May 2, 2021

May 2, 2021

Please add me to the list of members for the initial workgroup. Thank you, Raymond

2 1

In what tense should the changelog be written?
by Larry Hastings May 1, 2021

May 1, 2021

When one writes one's "blurb" for the changelog, in what tense should it be? I mostly see entries in present tense: bpo-43660: Fix crash that happens when replacing sys.stderr with a callable that can remove the object while an exception is being printed. Patch by Pablo Galindo. bpo-41561: Add workaround for Ubuntu’s custom OpenSSL security level policy. But occasionally I see entries in past tense: bpo-26053: Fixed bug where the pdb interactive run command echoed the args from the shell command line, even if those have been overridden at the pdb prompt. bpo-40630: Added tracemalloc.reset_peak() to set the peak size of traced memory blocks to the current size, to measure the peak of specific pieces of code. I couldn't find any guidance in the Python Dev Guide after sixty seconds of poking around. Obviously this isn't a big deal. But it might be nice to try and nudge everybody in the same direction. It'd be pleasant if the changelog read in a more unified voice, and using the same tense and sentence structure would help towards that goal. If we arrived at a firm decision, maybe "blurb" et al could add a little text suggesting the proper style. Cheers, //arry/

14 19