delta/cpython.git/Objects/unicodeobject.c, branch v2.7 Fix extra space. 2010-06-26T18:44:42+00:00 Ezio Melotti ezio.melotti@gmail.com 2010-06-26T18:44:42+00:00 0b5f32fe5882b8d24fdf6b9f354d32bf7a7d41a3 






fix warning with ucs4
2010-06-12T17:47:06+00:00

Benjamin Peterson
benjamin@python.org

2010-06-12T17:47:06+00:00

7989c01efcf22e671e57688f0287610e64da9db3












Issue #8941: decoding big endian UTF-32 data in UCS-2 builds could crash
2010-06-11T21:42:26+00:00

Antoine Pitrou
solipsis@pitrou.net

2010-06-11T21:42:26+00:00

d6f3aa2e45d501094ecb43e051394136e1d5a799

the interpreter with characters outside the Basic Multilingual Plane
(higher than 0x10000).





the interpreter with characters outside the Basic Multilingual Plane
(higher than 0x10000).







Update PyUnicode_DecodeUTF8 from RFC 2279 to RFC 3629.
2010-06-05T17:51:07+00:00

Ezio Melotti
ezio.melotti@gmail.com

2010-06-05T17:51:07+00:00

c8cc931ab39884089a8aa01de90c4e635c4089c1

1) #8271: when a byte sequence is invalid, only the start byte and all the
   valid continuation bytes are now replaced by U+FFFD, instead of replacing
   the number of bytes specified by the start byte.
   See http://www.unicode.org/versions/Unicode5.2.0/ch03.pdf (pages 94-95);
2) 5- and 6-bytes-long UTF-8 sequences are now considered invalid (no changes
   in behavior);
3) Add code and tests to reject surrogates (U+D800-U+DFFF) as defined in
   RFC 3629, but leave it commented out since it's not backward compatible;
4) Change the error messages "unexpected code byte" to "invalid start byte"
   and "invalid data" to "invalid continuation byte";
5) Add an extensive set of tests in test_unicode;
6) Fix test_codeccallbacks because it was failing after this change.





1) #8271: when a byte sequence is invalid, only the start byte and all the
   valid continuation bytes are now replaced by U+FFFD, instead of replacing
   the number of bytes specified by the start byte.
   See http://www.unicode.org/versions/Unicode5.2.0/ch03.pdf (pages 94-95);
2) 5- and 6-bytes-long UTF-8 sequences are now considered invalid (no changes
   in behavior);
3) Add code and tests to reject surrogates (U+D800-U+DFFF) as defined in
   RFC 3629, but leave it commented out since it's not backward compatible;
4) Change the error messages "unexpected code byte" to "invalid start byte"
   and "invalid data" to "invalid continuation byte";
5) Add an extensive set of tests in test_unicode;
6) Fix test_codeccallbacks because it was failing after this change.







Remove an unneeded variable and assignment.
2010-05-04T01:16:51+00:00

Brett Cannon
bcannon@gmail.com

2010-05-04T01:16:51+00:00

6983aea22b80360b76c0edec5cde1466e8ba1f06

Found using Clang's static analyzer.





Found using Clang's static analyzer.







more _PyString_Resize error checking
2010-04-03T00:57:33+00:00

Benjamin Peterson
benjamin@python.org

2010-04-03T00:57:33+00:00

e02da9669aac78dee544edfd147f671f702177b5












#7643: Unicode codepoints VT (0x0B) and FF (0x0C) are linebreaks according to Unicode Standard Annex #14.
2010-03-30T08:24:06+00:00

Florent Xicluna
florent.xicluna@gmail.com

2010-03-30T08:24:06+00:00

bbcf238a714148506b7d202fd3ee9881023a1f99












Backported PyCapsule from 3.1, and converted most uses of
2010-03-25T00:54:54+00:00

Larry Hastings
larry@hastings.org

2010-03-25T00:54:54+00:00

3bcff6ed52acaac596725dde0143e343cd4b1116

CObject to PyCapsule.





CObject to PyCapsule.







Issue #1583863: An unicode subclass can now override the __str__ method
2010-03-22T12:24:37+00:00

Victor Stinner
victor.stinner@haypocalc.com

2010-03-22T12:24:37+00:00

71deebb098e980cd6f9cd0330d6562cc0da8c310












#7649: "u'%c' % char" now behaves like "u'%s' % char" and raises a UnicodeDecodeError if 'char' is a byte string that can't be decoded using the default encoding.
2010-02-25T17:36:04+00:00

Ezio Melotti
ezio.melotti@gmail.com

2010-02-25T17:36:04+00:00

0d26e36a53c8d266f41c6cc2679b8c5b7e069847