This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients ezio.melotti, ned.deily, python-dev, roger.serwy, terry.reedy
Date 2020-06-07.03:56:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1591502170.48.0.106203807234.issue17506@roundup.psfhosted.org>
In-reply-to
Content
A suggestion: rather than trying to maintain a separate IDLE news file ("don't repeat yourself), it might be much easier to link to the IDLE section in each releases's formatted CHANGELOG now included in Python 3 docsets.  For example:

https://docs.python.org/3/whatsnew/changelog.html#idle
or
https://docs.python.org/3.8/whatsnew/changelog.html#idle

Yes, users would have to scroll down to each release's IDLE section but I suspect that wouldn't be a huge burden considering how infrequently change files are consulted.  To be even more useful, IDLE could first attempt to find the changelog in the Python installer's bundled copy of the docset like the F1 key does.  For example, with the macOS installer, the corresponding file URL is:

file:///Library/Frameworks/Python.framework/Versions/3.8/Resources/English.lproj/Documentation/whatsnew/changelog.html#idle
History
Date User Action Args
2020-06-07 03:56:10ned.deilysetrecipients: + ned.deily, terry.reedy, ezio.melotti, roger.serwy, python-dev
2020-06-07 03:56:10ned.deilysetmessageid: <1591502170.48.0.106203807234.issue17506@roundup.psfhosted.org>
2020-06-07 03:56:10ned.deilylinkissue17506 messages
2020-06-07 03:56:10ned.deilycreate