And here comes the option controlling the option expansion.
Note that configobj *was* implementing expansion for ${option} so we're not entering a completely unexplored territory when it comes to protection values against expansion.
We never had reports about expansion corrupting data since bzr started using configobj so I'm not *that* concerned about such occurrences with the {option} syntax, but if it can help landing this proposal...
And here comes the option controlling the option expansion.
Note that configobj *was* implementing expansion for ${option} so we're not entering a completely unexplored territory when it comes to protection values against expansion.
We never had reports about expansion corrupting data since bzr started using configobj so I'm not *that* concerned about such occurrences with the {option} syntax, but if it can help landing this proposal...