Skip to main content

Browse the archive

Staging
v0.5.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
PULL_REQUEST_TEMPLATE.md 
<!--
Thanks for your contribution!
Please read this comment in its entirety. It's quite important.

# Pull Request title

It should be in the following format:

```
bpo-NNNN: Summary of the changes made
```

Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.

Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

# Backport Pull Request title

If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format:

```
[X.Y] <title from the original PR> (GH-NNNN)
```

Where: [X.Y] is the branch name, e.g. [3.6].

GH-NNNN refers to the PR number from `master`.

-->
back to top