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 Arfrever, benjamin.peterson, brett.cannon, eric.araujo, ezio.melotti, python-dev, r.david.murray, vstinner
Date 2013-06-15.23:13:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371338039.54.0.874123516236.issue17177@psf.upfronthosting.co.za>
In-reply-to
Content
At this point I have updated all the code that does not directly exposes imp somehow or in Tools.

At this point the only thing I need to decide is whether I want to continue to expose the lock stuff from imp or leave it private. After that the pending deprecation is ready to go.
History
Date User Action Args
2013-06-15 23:13:59brett.cannonsetrecipients: + brett.cannon, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, Arfrever, r.david.murray, python-dev
2013-06-15 23:13:59brett.cannonsetmessageid: <1371338039.54.0.874123516236.issue17177@psf.upfronthosting.co.za>
2013-06-15 23:13:59brett.cannonlinkissue17177 messages
2013-06-15 23:13:59brett.cannoncreate