Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ConfigManager.set(where='override') #3970

Closed
mih opened this issue Dec 28, 2019 · 0 comments · Fixed by #3978
Closed

Support ConfigManager.set(where='override') #3970

mih opened this issue Dec 28, 2019 · 0 comments · Fixed by #3978
Labels
fix-implemented UX

Comments

@mih
Copy link
Member

mih commented Dec 28, 2019

Otherwise users need to know that this dance is needed to have any affect on a running instance:

(Pdb) cfg.overrides['datalad.log.level']= 'debug'
(Pdb) cfg.overrides
{'datalad.log.level': 'debug'}
(Pdb) cfg.get('datalad.log.level')
(Pdb) cfg.overrides
{'datalad.log.level': 'debug'}
(Pdb) cfg.reload()
(Pdb) cfg.get('datalad.log.level')
'100'
@mih mih added the UX label Dec 28, 2019
mih added a commit to mih/datalad that referenced this issue Jan 2, 2020
This brings the same (and actually more) configuration override
flexibility to the Python API that the cmdline API offers via
`datalad -c key=val`.

This feature is a necessity for being able to rely on one-off
configuration (changes) to alter command behavior, whenever
a dedicated command option is not absolutely needed or shall be
avoided.

A dedicated test for overrides is also included.

Fixes dataladgh-3970
@mih mih added the fix-implemented label Jan 2, 2020
@mih mih closed this as completed in #3978 Jan 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix-implemented UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant