[issue32917] ConfigParser writes a superfluous final blank line
Steven D'Aprano
report at bugs.python.org
Sat Mar 10 05:27:48 EST 2018
Steven D'Aprano <steve+python at pearwood.info> added the comment:
On Sat, Mar 10, 2018 at 06:37:28AM +0000, TitanSnow wrote:
>
> TitanSnow <tttnns1024 at gmail.com> added the comment:
>
> If we treat the original behavior as a bug,
> it’s much easier to write a patch
> that just changes the default behavior
> and never outputs a final blank line.
Remind me, why do we care about that extra blank line?
> I have looked through the testsuite of it.
> It seems that the original author had knew
> the final blank line and treat it as
> expect result. I’m not sure about it.
Is there a test for it? If so, then it should stay unless the author
agrees it can go, or we get approval on the Python-Dev mailing list.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32917>
_______________________________________
More information about the Python-bugs-list
mailing list