[New-bugs-announce] [issue17177] Document/deprecate imp

Brett Cannon report at bugs.python.org
Sun Feb 10 21:08:31 CET 2013

New submission from Brett Cannon:

I need a make a decision as to what (if anything) belongs in imp and then document what stays and deprecate everything else.

Everything in imp falls into one of the following categories:

* From importlib
  - get_magic()
  - source_from_cache()
  - cache_from_source()
* From sys
  - get_tag()
* Platform-implemented
  - lock_held()
  - acquire_lock()
  - release_lock()
  - Undocumented stuff related to builtins, frozen, and load_dynamic()
* Helper
  - reload()

The question is what to keep/expose in imp and what to deprecate. Basically I need to figure out what imp's role is supposed to be in the face of importlib. My gut says either expose platform-dependent stuff and reload() and move the rest to importlib/deprecate, or to completely do away with the module and force people to use the APIs in importlib for consistency (and to stop people from mucking around with import from outside of importlib).

assignee: brett.cannon
components: Library (Lib)
messages: 181849
nosy: brett.cannon
priority: normal
severity: normal
stage: test needed
status: open
title: Document/deprecate imp
versions: Python 3.4

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list