Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 0df1f4576ed2b12acc96cbfd732db247249ac573 authored by Miss Islington (bot) on 30 November 2018, 08:05:51 UTC, committed by GitHub on 30 November 2018, 08:05:51 UTC 
Fix typo in Memory Management doc. (GH-10798)
 
(cherry picked from commit a40700439195a119878150f4f0d425c42ca957ef)

Co-authored-by: Kevin Adler <kadler@us.ibm.com>
1 parent e604b6c
Raw File
Tip revision: 0df1f4576ed2b12acc96cbfd732db247249ac573 authored by Miss Islington (bot) on 30 November 2018, 08:05:51 UTC
Fix typo in Memory Management doc. (GH-10798)
Tip revision: 0df1f45
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