[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: Commited as r84443 (release27-maint), r8 (py3k) -- status: open -> closed ___ Python tracker ___ ___

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: Attached fix & test for Python 2; adjusting to Python 3 is trivial. The test could be added to 2.6 as well to protect against regressions there, though that's unlikely to be a significant issue. -- Added file: http://bugs.python.org/file18718/issu

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: I've attached a diagnostic script that I ran with Python 2.4..3.2 (current py3k HEAD); there are two output variants: "old style": [section] option = None "new style": [section] option This is the output I get when running this script f

[issue7005] ConfigParser does not handle options without values

Łukasz Langa added the comment: This one is strange. Trying to set a None value through set() raises 'TypeError: option values must be strings' on both Python 3.2 and 2.7. A string value of 'None' behaves as expected (e.g. correctly). -- ___ Python

[issue7005] ConfigParser does not handle options without values

Changes by Fred L. Drake, Jr. : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: Re-opening for investigation. (The previous message really should have been a new issue.) -- status: closed -> open ___ Python tracker ___

[issue7005] ConfigParser does not handle options without values

Dwayne Bailey added the comment: This is causing a regression in our code. Previously when we write out our INI file for an entry that has a value of None we saw the following: value = None These are now stored as: value This is now causing a traceback in our code. But interestingly I haven

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: Patch and documentation merged to the py3k branch (r78233). Work on this is complete. -- resolution: -> accepted stage: -> committed/rejected status: open -> closed type: -> feature request ___ Python tracker

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: Assigning to myself for handling. Bumping to Python 2.7 / 3.2 since support for this syntax variation is a new feature. -- assignee: -> fdrake versions: +Python 2.7, Python 3.2 -Python 2.6 ___ Python tracker

[issue7005] ConfigParser does not handle options without values

Mats Kindahl added the comment: So, what is the status on this? Who needs to review it? Is there anything I can do to get it accepted? Do I need to make any changes (in addition to those already suggested and done by fdrake)? -- ___ Python tracker <

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: I just looked at some MySQL configuration examples, and wonder if the guys that made that configuration-style choice were on crack. MySQL's syntax is sufficient justification for this feature (however abhorrent I consider it). (I've not read the patch.) -

[issue7005] ConfigParser does not handle options without values

Mats Kindahl added the comment: Adding patch with the changes requested by Fred. -- Added file: http://bugs.python.org/file14993/cfgparser-2.patch ___ Python tracker ___

[issue7005] ConfigParser does not handle options without values

Mats Kindahl added the comment: Fred L. Drake, Jr. wrote: > Fred L. Drake, Jr. added the comment: > > The test "value is not None" in line 620 (of the new version) could be > just "value" and get a little more value from less code. OK. > > I don't think I've ever run across a sample .ini-st

[issue7005] ConfigParser does not handle options without values

Mats Kindahl added the comment: I replied to the mail, but I don't know if it is attached to the issue, so I'll repeat here. I'll change the "value is not None" to just "value" where I used that idiom. The style of using options without values is quite common in my.cnf files used by MySQL prog

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: The test "value is not None" in line 620 (of the new version) could be just "value" and get a little more value from less code. I don't think I've ever run across a sample .ini-style file that used unspecified values, though it's frequently done in "flat" c

[issue7005] ConfigParser does not handle options without values

Changes by Fred L. Drake, Jr. : -- nosy: +fdrake ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue7005] ConfigParser does not handle options without values

New submission from Mats Kindahl : When ConfigParser is used to read in a my.cnf file (MySQL Server Configuration File), it fails for options that do not have value. ConfigParser is designed to require a value for each option, but some systems, such as MySQL option file reader, accepts options w