Message 218597 - 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	serhiy.storchaka
Recipients	ezio.melotti, kennyluck, loewis, serhiy.storchaka, vstinner
Date	2014-05-15.07:26:14
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
This issue was mainly resolved in issue12892. The surrogatepass error handler now works with UTF-16* and UTF-32* encodings. But for other encodings it behaves as for UTF-8 (preserve old behavior). Should we change the behavior for non-UTF encodings end raise an exception (as for "strict")?

This issue was mainly resolved in issue12892. The surrogatepass error handler now works with UTF-16* and UTF-32* encodings. But for other encodings it behaves as for UTF-8 (preserve old behavior). Should we change the behavior for non-UTF encodings end raise an exception (as for "strict")?

History
Date	User	Action	Args
2014-05-15 07:26:14	serhiy.storchaka	set	recipients: + serhiy.storchaka, loewis, vstinner, ezio.melotti, kennyluck
2014-05-15 07:26:14	serhiy.storchaka	set	messageid: <[email protected]>
2014-05-15 07:26:14	serhiy.storchaka	link	issue13916 messages
2014-05-15 07:26:14	serhiy.storchaka	create