Hi,

It's a bit late to produce a patch, but the bug in Config module is pretty simple: it's non-inheritable. The problem is that you don't use `self.method()` form of method calls where new Config instances are create. Instead you refer directly to the class itself: Config.method(). I have noticed this kind of calls in methods read, set, and unset.

I'd be really glad to see this fixed ASAP as I want to implement automated string values expansion for my local project but it's not possible because the first .read call results in the bare bones Config object.

Thank you!

Best regards,
Vadim Belman

On Wed, Mar 17, 2021 at 10:53:46PM -0400, Vadim Belman wrote:
> Hi,
> 
> It's a bit late to produce a patch, but the bug in Config module is pretty simple: it's non-inheritable. The problem is that you don't use `self.method()` form of method calls where new Config instances are create. Instead you refer directly to the class itself: Config.method(). I have noticed this kind of calls in methods read, set, and unset.
> 
> I'd be really glad to see this fixed ASAP as I want to implement automated string values expansion for my local project but it's not possible because the first .read call results in the bare bones Config object.
> 
> Thank you!
> 
> Best regards,
> Vadim Belman

I've updated the methods that call Config directly, to use self instead. This
change is part of v3.0.4, which I uploaded to CPAN just now.

-- 
With kind regards,

Patrick Spek


www:  https://www.tyil.nl/
mail: p.spek@tyil.nl
pgp:  1660 F6A2 DFA7 5347 322A  4DC0 7A6A C285 E2D9 8827

git:    https://git.tyil.nl/