Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 1fb312ce1f147ea84ecb6f5993a20d1a85c53dc3 authored by Miss Islington (bot) on 14 December 2018, 20:37:45 UTC, committed by Brett Cannon on 14 December 2018, 20:37:45 UTC 
bpo-35450: reflect in docs that venv module is not always creating a copy of the Python binary (GH-11144) (GH-11168)
 
 
 
 
 1 parent   f2df9b9 
  
 
 
  
  
 
   Raw File                
 
 
   
   
 
  
 Tip revision:  1fb312ce1f147ea84ecb6f5993a20d1a85c53dc3  authored by  Miss Islington (bot)  on 14 December 2018, 20:37:45 UTC 
 bpo-35450: reflect in docs that venv module is not always creating a copy of the Python binary (GH-11144) (GH-11168) 
 
 
 
 
  
 Tip revision:  1fb312c  
 
 
 
 
 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