Is there a way to force my interpreter (2.7) to import a module from site packages in case of a conflict? Let's say you are working with a directory structure like this:
top_level
----cool_mod
----init.py
----sweet_module.py
You already have sweet_module installed in the site packages. When running Python from this specific directory, if you use:
from cool_mod.sweet_module import *
You will import the local module instead of the global one. Is there any way to change this behavior?
This issue may come up in scenarios like:
top_level
setup.py
----cool_mod
----init.py
----sweet_module.py
Before installation, you can run cool_mod.sweet_module when your working directory is top_level. After installation, you should be able to import cool_mod.sweet_module from anywhere except this specific directory. However, even after installation, if you import from this directory, you will still get the local copy.