R. David Murray added the comment: 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. ---------- nosy: +r.david.murray _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17135> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
