This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lukasz.langa
Recipients Marc.Abramowitz, SilentGhost, lukasz.langa
Date 2016-05-02.23:19:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462231180.93.0.483662927199.issue26710@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-05-02 23:19:40lukasz.langasetrecipients: + lukasz.langa, SilentGhost, Marc.Abramowitz
2016-05-02 23:19:40lukasz.langasetmessageid: <1462231180.93.0.483662927199.issue26710@psf.upfronthosting.co.za>
2016-05-02 23:19:40lukasz.langalinkissue26710 messages
2016-05-02 23:19:40lukasz.langacreate