Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDLE subsection of What's New 3.11 #90653

Closed
terryjreedy opened this issue Jan 24, 2022 · 2 comments
Closed

IDLE subsection of What's New 3.11 #90653

terryjreedy opened this issue Jan 24, 2022 · 2 comments
Assignees
Labels
3.11 only security fixes topic-IDLE

Comments

@terryjreedy
Copy link
Member

BPO 46495
Nosy @terryjreedy

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 2022-01-24.02:51:38.367>
labels = ['3.11']
title = "IDLE subsection of What's New 3.11"
updated_at = <Date 2022-01-24.02:51:38.367>
user = 'https://github.com/terryjreedy'

bugs.python.org fields:

activity = <Date 2022-01-24.02:51:38.367>
actor = 'terry.reedy'
assignee = 'terry.reedy'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2022-01-24.02:51:38.367>
creator = 'terry.reedy'
dependencies = []
files = []
hgrepos = []
issue_num = 46495
keywords = []
message_count = 1.0
messages = ['411438']
nosy_count = 1.0
nosy_names = ['terry.reedy']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue46495'
versions = ['Python 3.11']

@terryjreedy
Copy link
Member Author

terryjreedy commented Jan 24, 2022

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.

@terryjreedy
Copy link
Member Author

See #95251 and discussion at end of #86012.

@terryjreedy terryjreedy closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.11 only security fixes topic-IDLE
Projects
Status: Done
Development

No branches or pull requests

2 participants