Q:

Is it possible to use two Python packages with the same name?

I have a question about imports.  The question might seem a bit contrived, but its purpose is to explore the limitations of using absolute imports for all imports in a package.  PEP8 highly discourages relative imports (edit: and the Google Python Style Guide says never to use them).
Say you are given two large-ish packages that both have the same name and that both use absolute imports in accordance with PEP8:

    /pkg1
        mod1.py (contains an absolute import: 'import pkg1.mod2')
        mod2.py
        ...

    /pkg1
        mod1.py (contains an absolute import: 'import pkg1.mod3')
        mod3.py
        ...

Also say you are working on a Python project in which you'd like to use both packages.  This could come up, say, if you want to use two versions of the same package in a project.
Is there a way to incorporate both packages into your project hierarchy so that you can freely use modules from both packages throughout your project?
For the solution it's acceptable to do things like use import aliases and modify sys.path temporarily.  But it's not okay to change the contents of either package directory.

A:

The short answer is no, Python doesn't accept two packages with the same name. (There are things called "namespace packages" that let a single package be implemented over multiple directories but they require the packages involved to be set up to cooperate with each other).
The way PEP 8 discourages explicit relative imports is one of its more questionable pieces of advice, precisely because it makes it harder to rename a package to avoid naming conflicts. If the two packages used relative imports, you could just rename one of them or nest it inside another package and be done with it.
import aliases won't help you here, because it is the name that ends up in sys.modules that matters, and that uses the name of the module as imported, rather than the name that ends up being bound in the importing module.
If you wanted to get really exotic, you could write your own importer (see PEP 302 and the 3.x importlib documentation). If you decide to go that far, you can do pretty much anything you want.

