Skip to main content

Browse the archive

Staging
v0.8.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 226a012d1cd61f42ecd3056c554922f359a1a35d authored by Brandt Bucher on 05 December 2020, 03:45:57 UTC, committed by GitHub on 05 December 2020, 03:45:57 UTC 
bpo-42536: GC track recycled tuples (GH-23623)
 
Several built-in and standard library types now ensure that their internal result tuples are always tracked by the garbage collector:

- collections.OrderedDict.items
- dict.items
- enumerate
- functools.reduce
- itertools.combinations
- itertools.combinations_with_replacement
- itertools.permutations
- itertools.product
- itertools.zip_longest
- zip

Previously, they could have become untracked by a prior garbage collection.
1 parent 2de5097
Raw File
Tip revision: 226a012d1cd61f42ecd3056c554922f359a1a35d authored by Brandt Bucher on 05 December 2020, 03:45:57 UTC
bpo-42536: GC track recycled tuples (GH-23623)
Tip revision: 226a012
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