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 terry.reedy
Recipients ncoghlan, terry.reedy
Date 2014-05-31.20:03:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401566588.31.0.436459410689.issue21621@psf.upfronthosting.co.za>
In-reply-to
Content
In #21569, revising What's New for 2.7, Nick is planning to add the following:

+PEP 434: IDLE Enhancement Exception for All Branches
+----------------------------------------------------
+
+:pep:`434` describes a general exemption for changes made to the IDLE
+development environment shipped along with Python. This exemption makes it
+possible for the IDLE developers to provide a more consistent user
+experience across all supported versions of Python 2 and 3.
+
+For details of any IDLE changes, refer to the NEWS file for the specific
+release.

I think the same should be added to What's New 3.4+ so Idle users are warned and informed that there might be otherwise unexpected changes. At minimum, the last phrase should be changed to "refer to the successive Idle sections of the changelog", where changelog' is linked as it is at the top of the file.

I am not sure where to put this. The 3.4 What's New has no Idle section. I did not think to write one :-(. Of course, there was almost nothing new since the previous 3.3.x bugfix release. I guess such a section should be a cumulative summary what was added since the previous x.y.0 release, even if all went into one of the bugfix releases, including the pending final maintenance release.
History
Date User Action Args
2014-05-31 20:03:08terry.reedysetrecipients: + terry.reedy, ncoghlan
2014-05-31 20:03:08terry.reedysetmessageid: <1401566588.31.0.436459410689.issue21621@psf.upfronthosting.co.za>
2014-05-31 20:03:07terry.reedylinkissue21621 messages
2014-05-31 20:03:06terry.reedycreate