[issue11027] Implement sectionxform in configparser

2011-01-28 Thread Kunjesh Kaushik
Kunjesh Kaushik kunjesh.kaus...@gmail.com added the comment: Very well, then. I would rely on sub-classing for now. The patch would work for me as I am only reading configuration. :) And yes, I wouldn't deny the personal bias anyway. Thanks a lot for all your help, folks. Keep up the good

[issue11027] Allow spaces around section header in ConfigParser

2011-01-27 Thread Kunjesh Kaushik
New submission from Kunjesh Kaushik kunjesh.kaus...@gmail.com: It is often desirable to be able to write a section with spaces around the header, as in [ default ] instead of [default] for the sake of readability of configuration file. I am not sure if this is the standard format

[issue11027] Allow spaces around section header in ConfigParser

2011-01-27 Thread Kunjesh Kaushik
Kunjesh Kaushik kunjesh.kaus...@gmail.com added the comment: Mr. Raymond has raised a valid point. On second thought, I think the submitted patch won't resolve the issue. import re r = re.compile(r'\[\s*(?Pheader[^]]+)\s*\]') # as in the patch r.match('[ section header ]').group('header

[issue11027] Allow spaces around section header in ConfigParser

2011-01-27 Thread Kunjesh Kaushik
Kunjesh Kaushik kunjesh.kaus...@gmail.com added the comment: I think we are dealing with two separate issues: a feature request for sectionxform kind of functionality desirable in a future release (3.3 maybe) and a behaviour issue in current releases (2.x and 3.x both). I suggest we split