Message 231652 - Python tracker

➜

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	ncoghlan
Recipients	amaury.forgeotdarc, ethan.furman, ezio.melotti, lemburg, ncoghlan, serhiy.storchaka, steven.daprano, vstinner
Date	2014-11-25.10:58:26
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1416913107.2.0.613331618562.issue19676@psf.upfronthosting.co.za>
In-reply-to

Content
Patch looks good to me, too. As far as Amaury's question goes, isn't the general reverse operation the same as for the existing backslashreplace handler? That is, decode with the appropriate ASCII compatible encoding (since ASCII compatibility is needed for the escape sequences to be valid), then run the result through ast.literal_eval? (I'll grant we don't currently provide guidance on reversing backslashreplace either, but addressing that sounds like a separate question from this change)

Patch looks good to me, too.

As far as Amaury's question goes, isn't the general reverse operation the same as for the existing backslashreplace handler?

That is, decode with the appropriate ASCII compatible encoding (since ASCII compatibility is needed for the escape sequences to be valid), then run the result through ast.literal_eval?

(I'll grant we don't currently provide guidance on reversing backslashreplace either, but addressing that sounds like a separate question from this change)

History
Date	User	Action	Args
2014-11-25 10:58:27	ncoghlan	set	recipients: + ncoghlan, lemburg, amaury.forgeotdarc, vstinner, ezio.melotti, steven.daprano, ethan.furman, serhiy.storchaka
2014-11-25 10:58:27	ncoghlan	set	messageid: <1416913107.2.0.613331618562.issue19676@psf.upfronthosting.co.za>
2014-11-25 10:58:27	ncoghlan	link	issue19676 messages
2014-11-25 10:58:26	ncoghlan	create