I'm using the [DEFAULT] section for this type of thing, but it's a bit wonky IMO and doesn't seem to fit with PasteDeploy's world view. I wish there was an easy way to inherit or mixin config from another section *in the same config file* (yes, I could use `use` to inherit config from another file, but I don't want to maintain N separate config files).
Alternatively, the [DEFAULT] section could work the same way as when using ConfigParser directly, and Paste's "global config" could be pulled from a section called [global_conf] or something like that. That would de-conflate Paste's notion of global config from the normal semantics of the [DEFAULT] section. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/yxmrVIaIwosJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
