#3037: Multiple bugs in trac.config
---------------------------+------------------------------------------------
Reporter: athomas | Owner: athomas
Type: defect | Status: reopened
Priority: low | Milestone: 0.10
Component: general | Version: devel
Severity: minor | Resolution:
Keywords: global config |
---------------------------+------------------------------------------------
Changes (by athomas):
* priority: high => low
* status: closed => reopened
* resolution: fixed =>
* severity: major => minor
Comment:
Replying to [comment:9 mgood]:
> Why should't it fall back on the global config when an option is
removed? This would be consistent with the expected behavior when an
option is deleted from the file directly.
That is definitely one way to look at it, and when done manually, probably
expected. But from a programmatic perspective I think `remove()`ing an
item should be more explicit. eg. WebAdmin has
`self.config.remove('logging', 'log_level')` which may or may not actually
reset the log level, depending on the global setting. If `remove()` can't
be relied on to actually do the job, why have it? If its behaviour is to
reset to the default, perhaps it would be preferable to rename it to
`set_default()` or similar.
''(also unclosing this ticket, but lowering priority/severity as now the
first two issues are closed it's not that much of a problem)''
--
Ticket URL: <http://trac.edgewall.org/ticket/3037#comment:11>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
