Thanks, I think that's fine--indeed the example is not correct. It might be worth keeping if the example were just changed to not try to use .set() the way it's doing. But I don't think we really need to encourage that usage anyways, especially given that it might change when we redo configuration....

This is actually a pretty serious bug in config. But I agree with @embray that this is an illustration of why we want to revamp config anyway (lots of configobj weirdness), so I'm fine with just merging it given it'll all change in the next version anyway.

@mwcraig - A quick tip: if you include the text closes #1567 in one of the commit messages (usually I do this on the second line so that it doesn't clutter the single-line commit log), it will automatically close the issue when this is merged. Helps with the bookeeping just a bit.