Using iniparse is not that simple -- see my bug closing and then reopening.
Oh, didn’t catch that. I though there was compatibility code for
configparser drop-in replacement.
Also, upstream is not doing any work on 1.7 anymore, unless serious bugs pop
up. Thus, forwarding the bug upstream does
On Sunday 07 March 2010 20:15:53, Éric Araujo wrote:
> Hello
Hello,
> Could you forward the bug upstream? (I checked on launchpad.net, since
> Wicd’s sourceforge page tells development happens there, and didn’t
> found this bug/request.) Upstream could then choose to include my 5-line
> patch or
Hello
Could you forward the bug upstream? (I checked on launchpad.net, since
Wicd’s sourceforge page tells development happens there, and didn’t
found this bug/request.) Upstream could then choose to include my 5-line
patch or depend on iniparse, to the benefit of all users.
Regards
--
To
3 matches
Mail list logo
