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 r.david.murray
Recipients ezio.melotti, r.david.murray, rhettinger, tshepang, vstinner
Date 2013-03-24.18:16:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Oh, it looks like you are right: useless strings are already removed 
> during compilation. But it looks a little bit surprising to me to use a 
> multiline string for a comment. I prefer classic # comments.

I was surprised by this as well.  I think the comment in _header_value_parser was originally a docstring and got moved around during editing.  It should probably get changed to a block comment.

I could have sworn that when I learned about the optimization it was in the context of documentation that specifically said the optimization was done so that triple quoted strings could be used as multi-line comments, but I cannot find it through google or guessing where I might have seen it in our docs, so perhaps I was imagining things.
Date User Action Args
2013-03-24 18:16:06r.david.murraysetrecipients: + r.david.murray, rhettinger, vstinner, ezio.melotti, tshepang
2013-03-24 18:16:06r.david.murraysetmessageid: <>
2013-03-24 18:16:06r.david.murraylinkissue17516 messages
2013-03-24 18:16:06r.david.murraycreate