> David Goodger wrote:
>> added_stylesheet_paths = path/with spaces/stylesheet.css
>> another/path/with spaces/stylesheet.css
>> c:/yet another/path, with punctuation/
>> One setting (path, URL) per line.
> Oh, I meant "one key=value pair per line."
> I didn't know that this syntax was allowed at all, and in most cases
> newlines are equivalent to spaces and are just a convenience to
> allow for wrapping. So I'd expect the above example to be
> equivalent with ::
> added_stylesheet_paths = path/with spaces/stylesheet.css
> added_stylesheet_paths = path/with spaces/stylesheet.css c:/yet
> another/path, with punctuation/
(That doesn't make sense. Bad edit?)
> So, as a user, I'd find this newline syntax hard to memorize.
This sounds like an attempt at justification.
Try it, it's not equivalent. That interpretation would need special
support. Since it isn't currently supported, nobody could possibly
depend on interpreting newlines as spaces in config files, so we can
>> The problem with any other punctuation (semicolons, commas) is that
>> they *can* be used in paths.
> I have some files with commas on my hard disk, but semicolons are
> very uncommon (only one file has a semicolon in it here).
Uncommon isn't good enough.
> Semicolons may be more common in URLs, but still I think that
> semicolons are a much better separator than newlines.
I don't. It's obvious to me that newlines are the simplest and best
> If/when semicolons are needed, we can still allow quoting (or
It's not a matter of "if or when". If we use *any* character that can
be part of a file name, we have to implement escaping (quoting is too
much trouble to bother with; with quoting, you still have to implement
I'm willing to ignore the possibility of newlines in paths. I have
never seen one used. If a newline ever *is* used in a file or
directory name, it is almost certainly an error. As Adam wrote,
"people that use newlines in their filenames deserve the problems they
David Goodger <http://python.net/~goodger>