Centralized config package | External hooks for `platformdirs`, __package__, package_dir, etc. about dynaconf HOT 1 OPEN

Hello, sorry for the delay. I have looked at this but didn't know how to respond immediately.

This looks like a useful use case, but we don't provide a specific out-of-the-box solution for the problem as you describe. As a library, Dynaconf provides some features for handling config, such as getting config from multiple sources, merging then, lazy evaluating, defining validators, etc. I believe you could leverage those features to implement this kind of "extensible framework" that you want. And if there is any specific gap/feature that you feel is missing to support this, it might be easier to request and implement that (as opposed to this more complex proposal).

Your use case looks somehow similar to the project I work on.
It uses a plugin system for django, and it use dynaconf to layer the settings like (sorted by loading order):

1. base_settings from core (everything in here)
2. base settings from loaded plugins
3. settings defined by users (via their settings file or envvars).

Let me know if that's helpful.

from dynaconf.