On Thu, 2011-11-03 at 15:02 -0400, Rob Crittenden wrote:
> Martin Kosek wrote:
> > Current Answer Cache storing mechanism is not ideal for storing
> > non-trivial Python types like arrays, custom classes, etc.
> > RawConfigParser just translates values to string, which
> > are not correctly decoded
Martin Kosek wrote:
Current Answer Cache storing mechanism is not ideal for storing
non-trivial Python types like arrays, custom classes, etc.
RawConfigParser just translates values to string, which
are not correctly decoded when the Answer Cache is parsed and
restored in the installer.
This pat
Current Answer Cache storing mechanism is not ideal for storing
non-trivial Python types like arrays, custom classes, etc.
RawConfigParser just translates values to string, which
are not correctly decoded when the Answer Cache is parsed and
restored in the installer.
This patch replaces RawConfigP
