ImportError's in part files are intercepted by django

[systemsoverload]

Django will intercept any ImportError's raised in part files and not have any idea how to display which part file the ImportError came from.

Ex.

#01-base.py
from . import not_there  # raises ImportError

The above code will cause django NOT settingsd to display the following

ImportError: Could not import settings 'project.settings' (Is it on sys.path? Is there an import error in the settings file?): No module named not_there

[anthonyrisinger]

The ImportError is flowing thru install(...), but even if we try/except and transform the ImportError to something else, it could not derive from ImportError otherwise Django is still going to eat it. I suppose Django assumes there is only one file so you know where the error must be :)

I'm not sure we should transform the exception, but it might be worth printing a warning/error if an ImportError is noticed? I could wrap the call to eval(...) that executes the part's code object:

https://github.com/xtfxme/settingsd/blob/master/settingsd/loaders.py#L40

[anthonyrisinger]

I have no idea what the above comment is talking about. Adding a dummy module to sys.modules and updating __file__ along the way might fix.