Łukasz Langa added the comment: Having both `defaults` and `overrides` would confuse the API, especially given that we already have `fallback` arguments to `get*` methods.
What's the point of having overrides *over* a file? Defaults were thought of as a way to say: "unless the user bothered to modify those, the values are as follows". That's the point of configuration. We have defaults, that the *user* overrides. Why would you want to override what the user specified? I fail to understand the logic behind this. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26710> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
