Package: importlib2
importlib2==========A complete backport to 2.7 (and 3.x) of the ``importlib`` package fromPython 3.  Compatibility is intended to match only the latest public,non-deprecated importlib API.Note: This project is not yet released and the code base may beunstable.  Currently the importlib tests all pass, but a few thingsremain to be done before the initial release.Note: Currently there is a problem under Python 3.2 with loadingmodules from .pyc files.  However, this does not affect 2.7, which isthe main target for importlib2.Usage-----You may use ``importlib2`` as you would any other module.  You may alsocall ``importlib2.hook.install()`` to make Python use ``importlib2`` forthe import system.API---See https://docs.python.org/dev/library/importlib.html.Be aware that deprecated importlib APIs have not been backported.Building and Installing-----------------------Use setup.py/pip/setuptools like normal.Extra Files-----------``importlib2`` adds the following files to ``importlib`` (relative topackage's root directory):* ``_fixers/`` - the code used to monkeypatch importlib2 at run-time* ``_version/__init__.py`` - contains the ``importlib2`` versioninformation* ``_version/ORIGINAL_PY_VERSION`` - the major/minor/micro version of thecpython from which ``importlib2`` was most recently pulled* ``_version/ORIGINAL_PY_REVISION`` - the revision of the cpython repofrom which ``importlib2`` was most recently pulled* ``_version/RELEASE`` - the ``importlib2`` release identifier relativeto ``ORIGINAL_PY_VERSION`` (an increasing integer)from which ``importlib2`` was most recently pulled* ``hook.py`` - the module used to set ``importlib2`` as Python's importsystem (not in the ``clean-cpython`` branch)Tools-----Each is located in the project root.* ``pull-cpython.py`` (only in the ``clean-cpython`` branch)* ``tests/`` (run ``python -m tests``)Main Branches-------------* ``clean-cpython`` - the relevant importlib files pulled from a cpythonrepo* ``standalone-3.4`` - the files fixed so that the test suite passesusing the Python interpreter built from the same cpython repo* ``default`` - the files fixed to work under 2.7Releases are made from the default branch.Merging from cpython--------------------1. from the ``clean-cpython`` branch run ``pull-cpython.py``2. commit the change3. change to the ``standalone-3.4`` branch4. merge from the ``clean-cpython`` branch5. make any changes necessary to get the test suite to pass usingthe same cpython from which the files were most recently pulled6. commit the changes (if any)7. change to ``default``8. merge from the ``standalone-3.4`` branch9. make any changes necessary to get the test suite to pass usingPython 2.7 (and 3.2)10. commit the changes (if any)Releasing---------<TBD>Contributing------------Contributions are very welcome.  That said, my intent is that theproject start out stable and that the API mirror that of importlib asclosely as possible.  So if I've done things right there won't be muchneed for contribution! :)Regardless, I'm definitely interested in bug reports and I'd be glad totake any feedback.  If you have a patch, definitely send a pull request.If you have any suggestions on improving the importlib API, you may opena ticket in the project tracker, but your best bet would be to open anissue upstream on `Python's bug tracker`_ (add eric.snow andbrett.cannon to the nosy list)... _Python's bug tracker:: https://bugs.python.orgReporting Issues and Feedback-----------------------------You may report bugs/suggestions/etc. issues to the project issuetracker:https://bitbucket.org/ericsnowcurrently/importlib2/issuesIf that doesn't fit, you can either take the matter to theimport-sig@python.org `mailing list`_ or email me directly atericsnowcurrent@gmail.com... _mailing list: https://mail.python.org/mailman/listinfo/import-sigAcknowledgements----------------A special thanks goes to Brett Cannon who went through the painstakingwork of taking CPython's import machinery and turning it into a purePython library, importlib.  His efforts over the course of several yearsbore fruit in Python 3.1 with the addition of importlib to the standardlibrary and culminated in the use of importlib as Python's importmachinery starting in Python 3.3.  Furthermore, without importlib'sthorough test suite importlib2 would have been essentially infeasible.Thanks Brett!