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

section inheritance #8

Merged
merged 9 commits into from
Jul 12, 2016
Merged

Conversation

buhman
Copy link
Collaborator

@buhman buhman commented Jul 8, 2016

implements #6

I think the best way to re-summarize why this is awesome by showing you this actually valid config.

This may or may not break compatibility with python<=3.2; we might need to make hubble depend on the backported configparser from 3.3 for this to work on obsolete python versions, or maybe add some even uglier hacks. done.

We should also consider breaking most of config out into a separate library, with proper unit testing. I'd also like to gut parts of shell into this new config library as well.

merge #7 first for a sane diff

@buhman buhman force-pushed the section-inheritance branch 2 times, most recently from 76e52ef to a8e54ed Compare July 12, 2016 01:27
@buhman buhman mentioned this pull request Jul 12, 2016
Merged
This adds a new InheritanceConfigParser, which supports section
inheritance. This also includes nested and multiple-inheritance.
This:

 - makes SafeConfigParser inherit from InheritanceConfigParser removes
 - removes redundant logic to add the default config section to the environment
 - removes duplicate definitions of the default section name

This also deduplicates logic spread between RawConfigParser.items() and
the RawConfigParser.get() call stack.
This replaces six.moves.configparser with configparser.

A direct reference to str was also replaced with a method call to that
object.
@thrawn01 thrawn01 merged commit 270324e into thrawn01:master Jul 12, 2016
This was referenced Jul 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants