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 Timothy.Gates, orsenthil, pje, r.david.murray
Date 2010-12-29.14:18:32
SpamBayes Score 2.4290478e-06
Marked as misclassified No
Message-id <1293632316.53.0.12395906231.issue10753@psf.upfronthosting.co.za>
In-reply-to
Content
In this case I think it is safe enough, since it only results in the ;,= not getting encoded.  If an application were doing anything with the encoded chars, it would probably be decoding them, and now that step will simply become a noop.  Of course, breakage is always possible, but this change seems worth what appears to be a relatively small risk.
History
Date User Action Args
2010-12-29 14:18:36r.david.murraysetrecipients: + r.david.murray, pje, orsenthil, Timothy.Gates
2010-12-29 14:18:36r.david.murraysetmessageid: <1293632316.53.0.12395906231.issue10753@psf.upfronthosting.co.za>
2010-12-29 14:18:32r.david.murraylinkissue10753 messages
2010-12-29 14:18:32r.david.murraycreate