Issue #6: ConfigParser Doesn't Read [Servers] Correctly - pyjigdo - Pagure.io

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

pyjigdo

#6 ConfigParser Doesn't Read [Servers] Correctly

Closed: Fixed Opened Oct 14, 2007 by jsteffan.

So, ConfigParser doesn't allow multiple entries for a option in a section. What can we do about this. Right now, only the last server listed in [Servers] (per option) is in our config object. This pretty much breaks the fallback support when defining servers.

jsteffan commented Oct 14, 2007

It has been recommend we look at iniparse

jsteffan commented Nov 25, 2007

Fixed in e8ff7a7045121f854d0f2442c52988b26994a06f

somebody commented Mar 22, 2009

Milestone Alpha Test deleted

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Priority

None

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.