gh-95251: IDLE - Add What's New section to README #95688
Conversation
Document what I (TJR) currently do for 3.10/3.11.
terryjreedy
added
skip news
needs backport to 3.10
|
@erlend-aasland Any suggestions on the text? |
There was a problem hiding this comment.
I left some comments. Looks good according to existing practice.
Digression: I'm not sure if the existing practice is the best practice; the IDLE What's New workflow look overly complicated, IMHO. I don't have a suggestion for how to simplify it; this is just my initial reaction.
Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
|
The are two What's New complications due the backport rule. When do entries start in the IDLE section? IDLE actually follows the same rule as the rest of Python. I tried to explain this better in the rewrite. Do we add entries for backported features? When What's New was a shorter summary initially drafted by editors, no. When provisional async got 'New in 3.x.y' entries, I started the same for IDLE. In 3.9, I simplified divider line to the one line for all post .0 backports. The point is to help people who upgrade see what might be new to them. |
|
Thanks @terryjreedy for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
|
GH-95726 is a backport of this pull request to the 3.11 branch. |
Document what I (TJR) currently do for 3.10/3.11. Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com> (cherry picked from commit a302a27) Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
|
GH-95727 is a backport of this pull request to the 3.10 branch. |
Document what I (TJR) currently do for 3.10/3.11. Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com> (cherry picked from commit a302a27) Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
Document what I (TJR) currently do for 3.10/3.11. Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
Document what I (TJR) currently do for 3.10/3.11.