Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision e57e50c8e77bc64e1ebab7a9ddf6f13fc3440c48 authored by Ezio Melotti on 05 June 2010, 17:51:07 UTC, committed by Ezio Melotti on 05 June 2010, 17:51:07 UTC 
Update PyUnicode_DecodeUTF8 from RFC 2279 to RFC 3629.
 
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 parent 3b818bf
Raw File
Tip revision: e57e50c8e77bc64e1ebab7a9ddf6f13fc3440c48 authored by Ezio Melotti on 05 June 2010, 17:51:07 UTC
Update PyUnicode_DecodeUTF8 from RFC 2279 to RFC 3629.
Tip revision: e57e50c
README.coverity 

Coverity has a static analysis tool (Prevent) which is similar to Klocwork.
They run their tool on the Python source code (SVN head) on a daily basis.
The results are available at:

     http://scan.coverity.com/

About 20 people have access to the analysis reports.  Other
people can be added by request.

Prevent was first run on the Python 2.5 source code in March 2006.
There were originally about 100 defects reported.  Some of these
were false positives.  Over 70 issues were uncovered.

Each warning has a unique id and comments that can be made on it.
When checking in changes due to a warning, the unique id
as reported by the tool was added to the SVN commit message.

False positives were annotated so that the comments can
be reviewed and reversed if the analysis was incorrect.

Contact python-dev@python.org for more information.
back to top