Ensure that distributions matching `requirements` are activated

`requirements` must be a string or a (possibly-nested) sequence
thereof, specifying the distributions and versions required.  The
return value is a sequence of the distributions that needed to be
activated to fulfill the requirements; all relevant distributions are
included, even if they were already activated in this working set.

Return a true filesystem path for specified resource

Declare that package 'packageName' is a namespace package

No Document.

Yield entry point objects from `group` matching `name`

If `name` is None, yields all entry points in `group` from all
distributions in the working set, otherwise only ones matching
both `group` and `name` are yielded (in distribution order).

Return specified resource as a string

A collection of active distributions on sys.path (or a similar list)

Return a readable file-like object for specified resource

Return a current distribution object for a Requirement or string

Convert a version string to a chronologically-sortable key

This is a rough cross between distutils' StrictVersion and LooseVersion;
if you give it versions that would work with StrictVersion, then it behaves
the same; otherwise it acts like a slightly-smarter LooseVersion. It is
*possible* to create pathological version coding schemes that will fool
this parser, but they should be very rare in practice.

The returned value will be a tuple of strings.  Numeric portions of the
version are padded to 8 digits so they will compare numerically, but(more...)

Object representing an advertised importable object

List the contents of the named resource directory

Wrap an actual or potential sys.path entry w/metadata

Does the named resource exist?

Searchable snapshot of distributions on a search path

Return an IResourceProvider for the named module or requirement

Ensure that the parent directory of `path` exists

Manage resource extraction and packages

Normalize a file/dir name for comparison purposes

Yield ``Requirement`` objects for each specification in `strs`

`strs` must be an instance of ``basestring``, or a (possibly-nested)
iterable thereof.