Description of problem:
ConfigParser behaviour changed for 2.7. It now allows key's with no value. See bug http://bugs.python.org/issue7005 and it seems that this is off by default.
In Virtaal we have a new bug 622061 which is being caused by the above change. We create and read the .ini file completely in code. So on first run we create virtaal.ini which previously in 2.6 would have an entry:
plural = None
It now has an entry:
When reading that entry we fail. So the patch implemented in issue7005 has not solved the problem completely and is allowing valueless key's on writing even though the parser is not configured to allow those.
Steps to Reproduce:
1. yum install virtaal
Virtaal crashes reading the .ini file it has just created.
Virtaal doesn't crash as ConfigParse doesn't change its behaviour.
My feeling is that this is an upstream regression and I've reported it there. I maintain the virtaal package on Fedora, my first thoughts where to try fix virtaal. But on investigation I feel that this is a Python regression which will show up across a number of packages. I'd rather not mask this by fixing virtaal.
A fix has been committed upstream:
The fix looks small and simple. I'll ping dmalcolm about whether he's okay with me updating f14 with this fix. From the bug, only python-2.7 needs it correct? Python-3.1 and Python-3.2 (when released) will be unaffected and python-2.6 has the old behaviour?
dmalcolm has approved -- I'll pull in the patch and make a new build. Due to the freeze for the beta release, it'll probably be a few weeks (after the beta) that the rebuild hits stable but it should show up in testing sooner.
python-2.7-8.fc14.1 has been submitted as an update for Fedora 14.
Please test hte update -- you can pull it straight out of koji for now (linked from the update request) or wait a day or two for it to be pushed to the f14 testing repository.
python-2.7-8.fc14.1 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update python'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/python-2.7-8.fc14.1
(In reply to comment #2)
> The fix looks small and simple. I'll ping dmalcolm about whether he's okay
> with me updating f14 with this fix. From the bug, only python-2.7 needs it
> correct? Python-3.1 and Python-3.2 (when released) will be unaffected and
> python-2.6 has the old behaviour?
I'm only working on 2.x series. From my reading 2.6 is unchanged, 2.7 needs the fix.
python-2.7-8.fc14.1 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.