Changes between Initial Version and Version 1 of Ticket #11538
- Timestamp:
- Mar 12, 2014, 10:01:12 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11538 – Description
initial v1 1 The sections of trac.ini allow duplicate options, with later values overwriting those that come first. Two patterns are possible, which could lead to confusing behavior when the user doesn't realize there the value is being redefined later in the file:1 The sections of trac.ini allow duplicate options, with later values overwriting those that come first. Two patterns that could lead to confusing behavior when the user doesn't realize that the option's value is being changed later in the file are: 2 2 1. Duplicate sections with the same option. 3 3 {{{#!ini … … 20 20 }}} 21 21 22 While Python 3.x has a much improved [http://docs.python.org/3.2/library/configparser.html configparser] module with a `strict` mode that raises an error when an option is redefined, I'm not sure there is much we can do in Python 2.x using `ConfigParser`.22 While Python 3.x has a much improved [http://docs.python.org/3.2/library/configparser.html configparser] module with a `strict` mode that raises an error when an option appears more than once, I'm not sure there is much we can do in Python 2.x using `ConfigParser`. 23 23 24 SO:5396653 suggests using a `dict_type` that allows multiple values with the same key, however `dict_type` is only supported in Python 2.6 .24 SO:5396653 suggests using a `dict_type` that allows multiple values with the same key, however `dict_type` is only supported in Python 2.6, so we wouldn't be able to apply as `dict_type`-based fix to 1.0-stable.
