Comment 3 for bug 801691

Just revisiting this as I was thinking about this previously. I think the best way forward here is to treat this as a comma-separated list of commandlines, where we parse each comma-separated string as a commandline.

So you can have messy configs like:

additional-options = --foo --bar, --baz

Which would be equivalent to:

additional-options = --foo --bar --baz

If a comma is required in an option, then quoting is needed:

additional-options = "--foo --bar --baz=,"

But this is the case already as configobj's list parsing is fairly simple.

In 1.1+ we can catch this error in the validator and raise a deprecation warning and eventually deprecate the comma separated approach entirely.

Still holding this sort of change off for a 1.1+ release.