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 brett.cannon, docs@python, eric.araujo, eric.snow, ktran13, r.david.murray
Date 2013-04-14.20:38:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365971931.43.0.912014031184.issue17135@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks, Kristian.  The 3.x docs were a "fresh start", so if we want to mark something as deprecated it would be a Python3 version number, the number current at the time of the deprecation.

There is another open issue, 17177, that speaks specifically about deprecating the module, but it sounds like a documentation deprecation to start with is a good idea; I believe that at this point all the imp functions can be replicated with suitable importlib calls (Eric can correct me if I'm wrong).  It would thus be as of version 3.4, at this point, since we didn't do it before the 3.3 release.

This issue also mentions linking to "importlib instead of the import statement", which refers to the ':keyword:`import`' statement in the title.

Do you want to resubmit the patch with those changes?  Otherwise I can just make them when I commit it.
History
Date User Action Args
2013-04-14 20:38:51r.david.murraysetrecipients: + r.david.murray, brett.cannon, eric.araujo, docs@python, eric.snow, ktran13
2013-04-14 20:38:51r.david.murraysetmessageid: <1365971931.43.0.912014031184.issue17135@psf.upfronthosting.co.za>
2013-04-14 20:38:51r.david.murraylinkissue17135 messages
2013-04-14 20:38:51r.david.murraycreate