IDLE subsection of What's New 3.10

[terryjreedy]

BPO	41846
Nosy	@terryjreedy, @miss-islington
PRs	bpo-41846: Update IDLE part of What's New 3.10 to 2022 #30906 [3.10] bpo-41846: Update IDLE part of What's New 3.10 to 2022 (GH-30906) #30907
Superseder	bpo-46495: IDLE subsection of What's New 3.11

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/terryjreedy'
closed_at = None
created_at = <Date 2020-09-23.14:32:22.387>
labels = ['expert-IDLE', '3.10', '3.11']
title = "IDLE subsection of What's New 3.10"
updated_at = <Date 2022-01-26.07:04:48.331>
user = 'https://github.com/terryjreedy'

bugs.python.org fields:

activity = <Date 2022-01-26.07:04:48.331>
actor = 'miss-islington'
assignee = 'terry.reedy'
closed = False
closed_date = None
closer = None
components = ['IDLE']
creation = <Date 2020-09-23.14:32:22.387>
creator = 'terry.reedy'
dependencies = []
files = []
hgrepos = []
issue_num = 41846
keywords = ['patch']
message_count = 1.0
messages = ['377390']
nosy_count = 2.0
nosy_names = ['terry.reedy', 'miss-islington']
pr_nums = ['30906', '30907']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = '46495'
type = None
url = 'https://bugs.python.org/issue41846'
versions = ['Python 3.10', 'Python 3.11']

[terryjreedy]

Following bpo-41844, master issue for IDLE entries in Doc/whatsnew/3.10.rst. This doc has a section 'Improved Modules' with a subsection 'idlelib and IDLE'. The initial unlabeled subsubsection includes important enhancements to IDLE since 3.9.0.

Because of IDLE's special backport policy (PEP-434), this initial part concludes with "The changes above have been backported to 3.9 maintenance releases." Future subsubsections 'New in 3.10.z:', z >= 1, will follow for backports to 3.10.z. These can precede the backport message as long as it is true. This issue will close after the last 3.10 maintenance release.

This file will always exists in the master branch. Changes are applied to master and backported as needed at the time. Entries will be the same in the What's New x.y for all x.y branches that get the enhancement. However, each file needs different backports. Hence separate PRs are needed for auto backport to work. It seems convenient to have separate issues for each.

[erlend-aasland]

Seems like this has been resolved with #30906 and #30907. Marking it as pending close.

[terryjreedy]

PEP-434 allows feature backports for IDLE.

[erlend-aasland]

Right.

I'm not sure why there is need for these "IDLE What's New" issues. If a feature is implemented, it surely has its own separate issue, coupled with a PR that is backported. Those PRs will surely be tied to the feature issue (not this issue), and so will the backport PRs. To justify the backports, you just need to reference PEP-434.

[terryjreedy]

Until about 3.7, What's New was mostly written by editors during the beta period. Individual IDLE changes were not listed until 3.6, when I started this series with #86012. #95251 is for moving the doc paragraphs to IDLE's README. Adding single versus multiple entries at a time is a matter of tradeoffs. For batch additions, I will try individual issues covering all current versions.