[Configobj-develop] Re: unrepr

[Kevin D. <da...@gm...>]

On 3/17/06, Michael Foord <fuz...@gm...> wrote:
> I can't just make this change because it's not backward compatible.
>
> I can add an 'unrepr' mode as an optional keyword (default False) that
> implements it.

Yes, this is what I was thinking.

> Currently ConfigObj doesn't keep a record of whether a value was quoted o=
r
> not, so it would take a bit of work to add this into the parsing code (an=
d
> the writing code). Not too difficult though.

If the unrepr mode is being used, the writing code should be able to
just use repr(). Parsing would be different, though...

> The code from CherryPy will probably be helpful to see how it detects
> 'convertible values'.

Yep. And that code is freely usable, as well.

Kevin