You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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=Nonecreated_at=<Date2022-01-24.02:51:38.367>labels= ['3.11']
title="IDLE subsection of What's New 3.11"updated_at=<Date2022-01-24.02:51:38.367>user='https://github.com/terryjreedy'
Following #86012, master issue for IDLE entries in Doc/whatsnew/3.11.rst. When appropriate, add subsection 'idlelib and IDLE' to 'Improved Modules' The initial entries include important enhancements to IDLE since 3.10.0. (Anything included in 3.10.0 does not belong here.
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.
3.11.rst will always exist in the master branch. Changes are applied to master and backported as needed at the time. Entries will normally 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 whatsnew/ file.
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: