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 r.david.murray
Recipients asvetlov, brian.curtin, gpolo, python-dev, r.david.murray, rhettinger, terry.reedy
Date 2012-03-29.19:19:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333048762.22.0.855161291421.issue3035@psf.upfronthosting.co.za>
In-reply-to
Content
Raymond is suggesting removal in 3.4, and given that we are doing it I don't see any reason to wait for 3.5, either, so you probably want to update the warning messages to say 3.4 instead of 3.5.  Otherwise it looks good to me.

Ezio suggested adding a test that fails if we don't do the deprecation in 3.4 (that is, when the feature release number changes, the test starts failing).  And/or you can open a new 3.4-only issue "remove deprecated tkinter functions" and mark it as a release blocker.
History
Date User Action Args
2012-03-29 19:19:22r.david.murraysetrecipients: + r.david.murray, rhettinger, terry.reedy, gpolo, brian.curtin, asvetlov, python-dev
2012-03-29 19:19:22r.david.murraysetmessageid: <1333048762.22.0.855161291421.issue3035@psf.upfronthosting.co.za>
2012-03-29 19:19:21r.david.murraylinkissue3035 messages
2012-03-29 19:19:21r.david.murraycreate