Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Implement more robust handling of config stages in Application #79

Closed
ipython opened this Issue · 2 comments

4 participants

@ipython

Original Launchpad bug 514903: https://bugs.launchpad.net/ipython/+bug/514903
Reported by: ellisonbg (Brian Granger).

Currently, we have various stages of config in our Application class. We need to refactor this to simplify the logic:

  • Create a bootstrap config object that contains things like ipython_dir
  • Have a single self.config object that hold the current state of the config. All code in Application should use this as the single source of config data while Application is being initialized.
  • As each config stage is completed, the config will always be merged into self.config.
  • We need to implement configuration key freezing to allow an Application to disallow particular config keys from changing.
@ellisonbg
Owner

Along with this, we need to reconsider the file format for config as well as the usage of config directories, etc.

@fperez
Owner

@ellisonbg, I made this critical since it will be part of the config work. We can close it once that's in.

@ellisonbg ellisonbg was assigned
@minrk minrk closed this issue from a commit
@minrk minrk Merge branch 'newapp'
closes gh-503
closes gh-454
closes gh-79
closes gh-456
closes gh-451
fbd5ae9
@minrk minrk closed this in fbd5ae9
@ellisonbg ellisonbg referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@mattvonrocketstein mattvonrocketstein referenced this issue from a commit in mattvonrocketstein/ipython
@minrk minrk Merge branch 'newapp'
closes gh-503
closes gh-454
closes gh-79
closes gh-456
closes gh-451
94a0a91
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.