[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2016-09-08 Thread Roundup Robot
Roundup Robot added the comment: New changeset 2150eadb54c7 by Serhiy Storchaka in branch 'default': Remove old typo. https://hg.python.org/cpython/rev/2150eadb54c7 -- nosy: +python-dev ___ Python tracker __

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2010-04-07 Thread Ezio Melotti
Changes by Ezio Melotti : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-b

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-06-15 Thread hippietrail
Changes by hippietrail : -- nosy: +hippietrail ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Benjamin Peterson
Benjamin Peterson added the comment: 2009/5/2 <"\"Martin v. Löwis\" "@psf.upfronthosting.co.za>: > > Martin v. Löwis added the comment: > >>> As for PyCodec_SurrogateErrors: I'd rather make it static than expose it. >> >> Why? All the other error handlers are exposed. > > Sure - but what for?

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Martin v. Löwis
Martin v. Löwis added the comment: >> As for PyCodec_SurrogateErrors: I'd rather make it static than expose it. > > Why? All the other error handlers are exposed. Sure - but what for? IMO, they all shouldn't be exposed. -- ___ Python tracker

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Benjamin Peterson
Benjamin Peterson added the comment: 2009/5/2 <"\"Martin v. Löwis\" "@psf.upfronthosting.co.za>: > > Martin v. Löwis added the comment: > > Committed as r72208, blocked as r72209. > > As for PyCodec_SurrogateErrors: I'd rather make it static than expose it. Why? All the other error handlers a

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Martin v. Löwis
Martin v. Löwis added the comment: Committed as r72208, blocked as r72209. As for PyCodec_SurrogateErrors: I'd rather make it static than expose it. -- resolution: -> accepted status: open -> closed ___ Python tracker

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Benjamin Peterson
Benjamin Peterson added the comment: Something I overlooked is that PyCodec_SurrogateErrors isn't exposed in any headers. -- ___ Python tracker ___ __

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Benjamin Peterson
Benjamin Peterson added the comment: I think the new patch looks fine. -- assignee: benjamin.peterson -> loewis ___ Python tracker ___ ___

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Martin v. Löwis
Changes by Martin v. Löwis : Added file: http://bugs.python.org/file13836/surrogates.diff ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Martin v. Löwis
Changes by Martin v. Löwis : Removed file: http://bugs.python.org/file13830/surrogates.diff ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-02 Thread Martin v. Löwis
Martin v. Löwis added the comment: Reviewers: report_bugs.python.org, Benjamin, Message: Issues fixed in r72188. http://codereview.appspot.com/52081/diff/1/5 File Doc/library/codecs.rst (right): http://codereview.appspot.com/52081/diff/1/5#newcode326 Line 326: In addition, the following error

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-01 Thread Benjamin Peterson
Benjamin Peterson added the comment: http://codereview.appspot.com/52081/diff/1/5 File Doc/library/codecs.rst (right): http://codereview.appspot.com/52081/diff/1/5#newcode326 Line 326: In addition, the following error handlers are specific to only selected "In addition, the following error hand

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-01 Thread Martin v. Löwis
Martin v. Löwis added the comment: Fixed indexing error. -- Added file: http://bugs.python.org/file13830/surrogates.diff ___ Python tracker ___ __

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-01 Thread Martin v. Löwis
Changes by Martin v. Löwis : Removed file: http://bugs.python.org/file13827/surrogates.diff ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-01 Thread Martin v. Löwis
Martin v. Löwis added the comment: rietveld: http://codereview.appspot.com/52081 -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-05-01 Thread Martin v. Löwis
Martin v. Löwis added the comment: Here is a patch that implements this proposed approach. It introduces a "surrogates" error handler, useful only for the utf-8 codec. If this is accepted, the implementation of PEP 383 can be simplified significantly, essentially removing the need for a separat

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-04-30 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: On 2009-04-29 22:39, Martin v. Löwis @psf.upfronthosting.co.za wrote: > Martin v. Löwis added the comment: > > I think we could preserve the marshal format with yet another error > handler - one that emits half surrogates into their intuitive form. That's

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-04-29 Thread Martin v. Löwis
Martin v. Löwis added the comment: I think we could preserve the marshal format with yet another error handler - one that emits half surrogates into their intuitive form. -- ___ Python tracker _

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-04-29 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: While it's probably ok to fix the codecs, there's an issue which makes this difficult at least for the utf-8 codec: The marshal module uses utf-8 to write Unicode objects and these can and need to be able to store the full range of supported UCS2/UCS4 code

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-04-28 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +lemburg, loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-04-28 Thread Antoine Pitrou
Antoine Pitrou added the comment: We could fix it for 3.1, and perhaps leave 2.7 unchanged if some people rely on this (for whatever reason). -- nosy: +pitrou priority: -> high stage: -> test needed versions: +Python 3.1 ___ Python tracker

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2009-04-25 Thread Jakub Wilk
Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2008-09-01 Thread Ezio Melotti
Changes by Ezio Melotti <[EMAIL PROTECTED]>: -- nosy: +ezio.melotti ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mail

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2008-08-24 Thread Adam Olsen
Changes by Adam Olsen <[EMAIL PROTECTED]>: -- components: +Unicode type: -> behavior ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pyt

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

2008-08-24 Thread Adam Olsen
New submission from Adam Olsen <[EMAIL PROTECTED]>: The Unicode FAQ makes it quite clear that any surrogates in UTF-8 or UTF-32 should be treated as errors. Lone surrogates in UTF-16 should probably be treated as errors too (but only during encoding/decoding; unicode objects on UTF-16 builds sho