path info according to `__file__`

Hi,

Above all, thank you for sharing this great package.
I have a setting according to the __file__, but the file location is not based on the file itself, but the include calling file. For example, when I have setting files as:

settings.__init__.py
settings/components/__init__.py
settings/components/common.py
settings/components/others.py

and if assume that include is calling components/common.py that contains the __file__ based setting. I expected the __file__ == settings/components/common.py but the actual value is settings.__init__.py.

if I have another setting in components/others.py and need to import from settings.components.common import VARS where the VARS is the setting based on __file__, then the value of the VARS becomes different.

Can I have any hint to solve this conflict? Thank you!

Reproduce the reported behavior using the settings layout shown: settings.init.py, settings/components/common.py, and settings/components/others.py. Start by tracing how include handles file when common.py is loaded, then verify whether importing VARS from others.py preserves the expected path-specific value. Done means the intended behavior is documented or the path resolution is corrected and covered by a regression test.