➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lukasz.langa
Recipients eric.araujo, grahamd, lukasz.langa
Date 2012-04-19.07:27:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334820430.12.0.573853336513.issue14590@psf.upfronthosting.co.za>
In-reply-to
Content 
INI files won't go away and there will come a time where 3.3 is old. Since 3.2 inline comments are turned off by default which mitigates the problem. Fixing this parser bug for the 3.3 release seems safe enough for me as long as you clearly state in NEWS and the docs that it changed. I'll leave 2.7 and 3.2 behind as to my doubts stated in the previous comment.
History
Date User Action Args
2012-04-19 07:27:10lukasz.langasetrecipients: + lukasz.langa, eric.araujo, grahamd
2012-04-19 07:27:10lukasz.langasetmessageid: <1334820430.12.0.573853336513.issue14590@psf.upfronthosting.co.za>
2012-04-19 07:27:09lukasz.langalinkissue14590 messages
2012-04-19 07:27:09lukasz.langacreate