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 brett.cannon
Recipients brett.cannon, kbk, roger.serwy, terry.reedy
Date 2013-05-25.22:54:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369522464.0.0.865118684304.issue18055@psf.upfronthosting.co.za>
In-reply-to
Content
If you would prefer to keep using imp in IDLE to make management across versions easier I'm fine with that, just understand my goal is to deprecate imp in Python 3.4 (but won't remove it until Python 4 so people can write Python 2/3 compatible code, much like you with IDLE). So if you're okay with using a deprecated module then this change is strictly not necessary and I can just silence any deprecation warning in the code instead when the deprecation comes about.
History
Date User Action Args
2013-05-25 22:54:24brett.cannonsetrecipients: + brett.cannon, terry.reedy, kbk, roger.serwy
2013-05-25 22:54:24brett.cannonsetmessageid: <1369522464.0.0.865118684304.issue18055@psf.upfronthosting.co.za>
2013-05-25 22:54:23brett.cannonlinkissue18055 messages
2013-05-25 22:54:23brett.cannoncreate