Support for semicolon based comments

[gau1991]

Now PHP uses semicolon separted comments it its ini file. When I am trying to read php.ini file, I am getting error

>>> config = ConfigObj('/etc/php5/fpm/php.ini')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.4/dist-packages/configobj.py", line 1229, in __init__
    self._load(infile, configspec)
  File "/usr/local/lib/python3.4/dist-packages/configobj.py", line 1318, in _load
    raise error
configobj.ConfigObjError: Parsing failed with several errors.
First error at line 3.

[EliAndrewC]

Adding an option to the ConfigObj class to specify the character(s) which begin a comment seems like a valid and useful feature. To be honest I'm not sure when the next time we'll be doing any major configobj work will be, but we can definitely tackle this when that happens if no one makes a pull request before then.

In the meantime, a workaround you could use would be to do something really hacky like

import re
from StringIO import StringIO
with open('/etc/php5/fpm/php.ini') as f:
    file_contents = re.sub('^;', '#', f.read())
config = ConfigObj(StringIO(file_contents))

but I understand that you may want to avoid this kind of hackery.

[gepd]

I've a file with ';' as market comment, I set the COMMENT_MARKERS with ['#', ';'] and when I write in the file, it ends with both markers

Ex. Initial comment:

; Comment Line 1
; Comment Line 2

After write in file:

# ; Comment Line 1
# ; Comment Line 2

I need to set both markers because some files I'm working with, starts with '#' and others ';'

[jhermann]

There are explicit tests for that, so your code does things differently than the test, or you use wrong versions. Check both.