| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
This is mostly from 257eb0c17 and 16d3e04cb to allow for setting arbitrary
database options since some settings require nested dictionaries, etc.
This got lost during merge from maint into master because of the completely
different Options parsing.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The database name is sometimes a path (SQLite) and sometimes not
(MySQL, PostgreSQL). This introduces a new Option type,
RepositoryMacroOption, that expands <repository> macros without
canonicalizing the path, so SQLite users can use <repository> in their
settings but MySQL users' database name settings will not be destroyed
by path canonicalization.
The unfortunate downside is that SQLite users can't use ~ in their
database name.
|
| |
|
|
|
|
| |
This fixes canonicalizing PathOption values when the default value of
a config file-only option is used. It also fixes PathOptions that get
a file-like object instead of a filename string.
|
| |
|
|
|
| |
This cleans up the temporary config files created by the option
parsing unit tests. Courtesy Alexander Sulfrian.
|
| |
|
|
|
|
|
| |
This fixes several cases in which <repository> macros would not be
properly processed: options that are not added to the parser yet when
early options are parsed; and config file options whose default value
is used.
|
| | |
|
| |
|
|
| |
This quiets down a lot of tests, especially for option parsing.
|
| | |
|
| | |
|
| |
|
