Imp(redirected from imp)

Imp definition: 1. A small evil spirit 2. A child that behaves badly, but in a way that is funny rather than. IMP majors also must complete the general requirements for a bachelor of arts degree from the College of Arts and Sciences. More about majors Individualized Minors. Add a personalized touch to your Indiana University degree by designing your own minor. IMP minors consist of 15 credit hours of coursework. Wilson is a primary doctor and pediatrician who also offers weight loss, Botox®, Juvederm®, Laser Hair Removal, Spider Vein Removal, and Clinical Cosmetics among other skincare packages. Imp definition, a little devil or demon; an evil spirit.

Also found in: Dictionary, Thesaurus, Medical, Financial, Acronyms, Encyclopedia, Wikipedia.

you little imp

An expression of dismay after someone (the 'imp') has done something surprising or has misbehaved in some way. I can't believe you got into my make-up drawer, you little imp!
Farlex Dictionary of Idioms. © 2015 Farlex, Inc, all rights reserved.
See also:

Want to thank TFD for its existence? Tell a friend about us, add a link to this page, or visit the webmaster's page for free fun content.
Link to this page:

Source code:Lib/imp.py

Deprecated since version 3.4: The imp module is deprecated in favor of importlib.

This module provides an interface to the mechanisms used to implement theimport statement. It defines the following constants and functions:


Return the magic string value used to recognize byte-compiled code files(.pyc files). (This value may be different for each Python version.)

Deprecated since version 3.4: Use importlib.util.MAGIC_NUMBER instead.


Return a list of 3-element tuples, each describing a particular type ofmodule. Each triple has the form (suffix,mode,type), where suffix isa string to be appended to the module name to form the filename to searchfor, mode is the mode string to pass to the built-in open() functionto open the file (this can be 'r' for text files or 'rb' for binaryfiles), and type is the file type, which has one of the valuesPY_SOURCE, PY_COMPILED, or C_EXTENSION, describedbelow.

Deprecated since version 3.3: Use the constants defined on importlib.machinery instead.

imp.find_module(name[, path])

Try to find the module name. If path is omitted or None, the list ofdirectory names given by sys.path is searched, but first a few specialplaces are searched: the function tries to find a built-in module with thegiven name (C_BUILTIN), then a frozen module (PY_FROZEN),and on some systems some other places are looked in as well (on Windows, itlooks in the registry which may point to a specific file).

Otherwise, path must be a list of directory names; each directory issearched for files with any of the suffixes returned by get_suffixes()above. Invalid names in the list are silently ignored (but all list itemsmust be strings).

If search is successful, the return value is a 3-element tuple (file,pathname,description):

file is an open file object positioned at the beginning, pathnameis the pathname of the file found, and description is a 3-element tuple ascontained in the list returned by get_suffixes() describing the kind ofmodule found.

If the module is built-in or frozen then file and pathname are both Noneand the description tuple contains empty strings for its suffix and mode;the module type is indicated as given in parentheses above. If the searchis unsuccessful, ImportError is raised. Other exceptions indicateproblems with the arguments or environment.

If the module is a package, file is None, pathname is the packagepath and the last item in the description tuple is PKG_DIRECTORY.

This function does not handle hierarchical module names (names containingdots). In order to find P.M, that is, submodule M of package P, usefind_module() and load_module() to find and load package P, andthen use find_module() with the path argument set to P.__path__.When P itself has a dotted name, apply this recipe recursively.

Deprecated since version 3.3: Use importlib.util.find_spec() instead unless Python 3.3compatibility is required, in which case useimportlib.find_loader(). For example usage of the former case,see the Examples section of the importlibdocumentation.

imp.load_module(name, file, pathname, description)

Load a module that was previously found by find_module() (or by anotherwise conducted search yielding compatible results). This function doesmore than importing the module: if the module was already imported, it willreload the module! The name argument indicates the fullmodule name (including the package name, if this is a submodule of apackage). The file argument is an open file, and pathname is thecorresponding file name; these can be None and ', respectively, whenthe module is a package or not being loaded from a file. The descriptionargument is a tuple, as would be returned by get_suffixes(), describingwhat kind of module must be loaded.

If the load is successful, the return value is the module object; otherwise,an exception (usually ImportError) is raised.

Important: the caller is responsible for closing the file argument, ifit was not None, even when an exception is raised. This is best doneusing a tryfinally statement.

Deprecated since version 3.3: If previously used in conjunction with imp.find_module() thenconsider using importlib.import_module(), otherwise use the loaderreturned by the replacement you chose for imp.find_module(). If youcalled imp.load_module() and related functions directly with filepath arguments then use a combination ofimportlib.util.spec_from_file_location() andimportlib.util.module_from_spec(). See the Examplessection of the importlib documentation for details of the variousapproaches.


Return a new empty module object called name. This object is not insertedin sys.modules.

Deprecated since version 3.4: Use importlib.util.module_from_spec() instead.


Reload a previously imported module. The argument must be a module object, soit must have been successfully imported before. This is useful if you haveedited the module source file using an external editor and want to try out thenew version without leaving the Python interpreter. The return value is themodule object (the same as the module argument).

When reload(module) is executed:

  • Python modules’ code is recompiled and the module-level code reexecuted,defining a new set of objects which are bound to names in the module’sdictionary. The init function of extension modules is not called a secondtime.

  • As with all other objects in Python the old objects are only reclaimed aftertheir reference counts drop to zero.

  • The names in the module namespace are updated to point to any new or changedobjects.

  • Other references to the old objects (such as names external to the module) arenot rebound to refer to the new objects and must be updated in each namespacewhere they occur if that is desired.

There are a number of other caveats:

When a module is reloaded, its dictionary (containing the module’s globalvariables) is retained. Redefinitions of names will override the olddefinitions, so this is generally not a problem. If the new version of a moduledoes not define a name that was defined by the old version, the old definitionremains. This feature can be used to the module’s advantage if it maintains aglobal table or cache of objects — with a try statement it can testfor the table’s presence and skip its initialization if desired:

It is legal though generally not very useful to reload built-in or dynamicallyloaded modules, except for sys, __main__ and builtins.In many cases, however, extension modules are not designed to be initializedmore than once, and may fail in arbitrary ways when reloaded.

If a module imports objects from another module using fromimport …, calling reload() for the other module does notredefine the objects imported from it — one way around this is to re-executethe from statement, another is to use import and qualifiednames (module.*name*) instead.

If a module instantiates instances of a class, reloading the module that definesthe class does not affect the method definitions of the instances — theycontinue to use the old class definition. The same is true for derived classes.

Changed in version 3.3: Relies on both __name__ and __loader__ being defined on the modulebeing reloaded instead of just __name__.

Deprecated since version 3.4: Use importlib.reload() instead.

The following functions are conveniences for handling PEP 3147Ipc a 610e free downloadwesternhunter. byte-compiledfile paths.

imp.cache_from_source(path, debug_override=None)

Return the PEP 3147 path to the byte-compiled file associated with thesource path. For example, if path is /foo/bar/baz.py the returnvalue would be /foo/bar/__pycache__/baz.cpython-32.pyc for Python 3.2.The cpython-32 string comes from the current magic tag (seeget_tag(); if sys.implementation.cache_tag is not defined thenNotImplementedError will be raised). By passing in True orFalse for debug_override you can override the system’s value for__debug__, leading to optimized bytecode.

path need not exist.

Changed in version 3.3: If sys.implementation.cache_tag is None, thenNotImplementedError is raised.

Deprecated since version 3.4: Use importlib.util.cache_from_source() instead.

Changed in version 3.5: The debug_override parameter no longer creates a .pyo file.

Picture of an imp

Given the path to a PEP 3147 file name, return the associated source codefile path. For example, if path is/foo/bar/__pycache__/baz.cpython-32.pyc the returned path would be/foo/bar/baz.py. path need not exist, however if it does not conformto PEP 3147 format, a ValueError is raised. Ifsys.implementation.cache_tag is not defined,NotImplementedError is raised.

Changed in version 3.3: Raise NotImplementedError whensys.implementation.cache_tag is not defined.

Deprecated since version 3.4: Use importlib.util.source_from_cache() instead.


Return the PEP 3147 magic tag string matching this version of Python’smagic number, as returned by get_magic().

Deprecated since version 3.4: Use sys.implementation.cache_tag directly startingin Python 3.3.

The following functions help interact with the import system’s internallocking mechanism. Locking semantics of imports are an implementationdetail which may vary from release to release. However, Python ensuresthat circular imports work without any deadlocks.


Return True if the global import lock is currently held, elseFalse. On platforms without threads, always return False.

On platforms with threads, a thread executing an import first holds aglobal import lock, then sets up a per-module lock for the rest of theimport. This blocks other threads from importing the same module untilthe original import completes, preventing other threads from seeingincomplete module objects constructed by the original thread. Anexception is made for circular imports, which by construction have toexpose an incomplete module object at some point.

Changed in version 3.3: The locking scheme has changed to per-module locks forthe most part. A global import lock is kept for some critical tasks,such as initializing the per-module locks.


Acquire the interpreter’s global import lock for the current thread.This lock should be used by import hooks to ensure thread-safety whenimporting modules.

Once a thread has acquired the import lock, the same thread may acquire itagain without blocking; the thread must release it once for each time it hasacquired it.

On platforms without threads, this function does nothing.

Changed in version 3.3: The locking scheme has changed to per-module locks forthe most part. A global import lock is kept for some critical tasks,such as initializing the per-module locks.


Release the interpreter’s global import lock. On platforms withoutthreads, this function does nothing.

Changed in version 3.3: The locking scheme has changed to per-module locks forthe most part. A global import lock is kept for some critical tasks,such as initializing the per-module locks.

The following constants with integer values, defined in this module, are usedto indicate the search result of find_module().


The module was found as a source file.

Deprecated since version 3.3.


The module was found as a compiled code object file.


The module was found as dynamically loadable shared library.

Deprecated since version 3.3.


The module was found as a package directory.


The module was found as a built-in module.

Deprecated since version 3.3.


The module was found as a frozen module.

class imp.NullImporter(path_string)

The NullImporter type is a PEP 302 import hook that handlesnon-directory path strings by failing to find any modules. Calling this typewith an existing directory or empty string raises ImportError.Otherwise, a NullImporter instance is returned.

Impeachment against trump

Instances have only one method:

find_module(fullname[, path])

This method always returns None, indicating that the requested module couldnot be found.

Changed in version 3.3: None is inserted into sys.path_importer_cache instead of aninstance of NullImporter.

Deprecated since version 3.4: Insert None into sys.path_importer_cache instead.


Impeachment Vote

The following function emulates what was the standard import statement up toPython 1.4 (no hierarchical module names). (This implementation wouldn’t workin that version, since find_module() has been extended andload_module() has been added in 1.4.)