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

Already on GitHub? Sign in to your account

Implement more robust handling of config stages in Application #79

ipython opened this Issue May 10, 2010 · 2 comments


None yet
4 participants

ghost commented May 10, 2010

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

ellisonbg commented Mar 24, 2011

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


fperez commented Apr 8, 2011

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

@ghost ghost assigned ellisonbg Apr 10, 2011

@minrk minrk closed this in fbd5ae9 Jun 21, 2011

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014

Merge branch 'newapp'
closes gh-503
closes gh-454
closes gh-79
closes gh-456
closes gh-451
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment