PEP420 - implicit namespace packages for python 2.7
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
docs
filefinder2
tests
.coveragerc
.gitignore
.travis.yml
CHANGELOG.rst
LICENSE
README.rst
requirements-dev.txt
setup.cfg
setup.py
tox.ini

README.rst

filefinder2

PEP420 - Implicit Namespace Packages for Python 2.7

tests Travis-CI Build Status Requirements Status Code Quality Status CodeCov Coveralls
Python PyPI Package latest release PyPI Package monthly downloads PyPI Wheel Supported versions Supported implementations

filefinder2 implements PEP 420 in Python2, and make every directory a namespace package, effectively mimicking Python3 behavior.

To do this, filefinder2 includes finder and loader hooks that contain the implicit namespace logic.

It is worth noting that we achieve this without pkg_resources or pkgutil, minimizing the dependencies necessary for that feature.

Usage:

import filefinder2

with filefinder2.Py3Importer():
    import namespace.package

Also filefinder2 provides some of python3 importlib API, even without "activating" it. For more details have a look inside the tests. There is a quite exhaustive usecase coverage.

Recent Upgrade Notes:

filefinder2 until recently had an API with an implicit model:

import filefinder2
# just works !

because we were able to do things like:

if sys.version_info < (3, 3):
    import filefinder2 as importlib
else:
    import importlib

# *should* just work for any python versions

However filefinder2 is not a standard library, and this model has proven to be quite tricky to use, given the little visibility an average developer has on the import sequence. And as a general rule, it is better to remain in control of our import system, and know what you are doing.

Therefore it was recently changed to an explicit model (using a context manager):

import filefinder2

with filefinder2.Py3Importer():
    # works ! but doesn't change anything in python3

# doesn't work any longer, if you are using python2

As a result, the check for the python interpreter version has been included inside filefinder2, instead of being expected of the user (which used to lead to tricks to install dependencies depending on version) This means the above code will work and do what you expect it to, no matter the version of Python you are running.