Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision b7874c809cbead0eb07554b61efe7823238c8bd9 authored by Miss Islington (bot) on 07 July 2018, 23:50:33 UTC, committed by GitHub on 07 July 2018, 23:50:33 UTC 
bpo-33888: Use CPython instead of Python in the FAQ (GH-7767)
 

Make the change where discussing the CPython implementation of lists and dicts.
(cherry picked from commit 8d41278045ee4e8bf1cadb58a7db58d70ad55237)

Co-authored-by: Andrés Delfino <adelfino@gmail.com>
1 parent becb527
Raw File
Tip revision: b7874c809cbead0eb07554b61efe7823238c8bd9 authored by Miss Islington (bot) on 07 July 2018, 23:50:33 UTC
bpo-33888: Use CPython instead of Python in the FAQ (GH-7767)
Tip revision: b7874c8
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