You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d5c8f14
Browse filesBrowse the repository at this point in the historyBrowse files
Merge branch 'main' into gc-debug-ft-race; address review
- Read gcstate->debug once into a local in delete_garbage,
handle_legacy_finalizers, gc_collect_main and _PyGC_DumpShutdownStats.
- Simplify the regression test to one gc.set_debug() writer racing one
gc.get_debug() reader via run_concurrently(), dropping the collector
thread.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug.yml
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ body:
16
16
Make sure to also search the [CPython issue tracker](https://github.com/python/cpython/issues?q=is%3Aissue+sort%3Acreated-desc) to check that the bug has not already been reported.
17
17
- type: textarea
18
18
attributes:
19
-
label: "Bug description:"
19
+
label: "Bug report"
20
20
description: >
21
21
Give a clear and concise description of what happened.
22
22
Include a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) if possible.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/crash.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -10,8 +10,9 @@ body:
10
10
The CPython interpreter is written in a different programming language, C. A "CPython crash" is when Python itself fails, leading to a traceback in the C stack.
11
11
- type: textarea
12
12
attributes:
13
-
label: What happened?
13
+
label: Crash report
14
14
description: >
15
+
Give a clear and concise description of what happened.
15
16
Include a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) if possible.
16
17
[Copy and paste code where possible rather than using screenshots](https://meta.stackoverflow.com/a/285557/13990016),
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ body:
12
12
Major feature proposals should generally be discussed on [Discourse](https://discuss.python.org/c/ideas/6) before opening a GitHub issue. Wait until it's clear that most people support your idea before filling in this form.
13
13
- type: textarea
14
14
attributes:
15
-
label: "Proposal:"
15
+
label: "Feature or enhancement"
16
16
description: >
17
17
Explain your proposal, why it should be implemented, and how it would be used.
description: Privately report a potential security vulnerability in CPython
3
+
body:
4
+
- type: markdown
5
+
attributes:
6
+
value: |
7
+
**Not all bugs are vulnerabilities.** Before submitting, read the [Python security policy](https://devguide.python.org/security/policy/) to understand which issues are vulnerabilities and what versions of Python accept reports.
8
+
9
+
Keep the report short and in plain text: no headers, tables, PDFs, binaries, or severity and CVSS information.
10
+
11
+
Reports that do not contain a potential security vulnerability will be discarded without a reply.
12
+
13
+
To report vulnerabilities that affect other projects (such as pip or python.org), or if you are not sure where to send your report, email [security@python.org](mailto:security@python.org).
14
+
- type: textarea
15
+
id: summary
16
+
attributes:
17
+
label: Summary
18
+
description: A few sentences describing the vulnerability.
19
+
validations:
20
+
required: true
21
+
- type: textarea
22
+
id: threat_model
23
+
attributes:
24
+
label: Threat model
25
+
description: >
26
+
What does the attacker control, and what do they gain? Describe the code, configuration, or deployment that may exist in the real world and is exploitable. Where possible, cite the relevant part of the [security policy](https://devguide.python.org/security/policy/#what-types-of-bugs-are-vulnerabilities).
27
+
validations:
28
+
required: true
29
+
- type: textarea
30
+
id: proof_of_concept
31
+
attributes:
32
+
label: Proof of concept
33
+
description: >
34
+
A script that reproduces the issue and clearly indicates whether the vulnerability is present, such as exiting with `1` if vulnerable and `0` if not. If it depends on a specially constructed binary file, include a script to construct the file rather than the file itself.
35
+
36
+
Wrap scripts longer than a few lines in a [collapsed section](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections) using `<details> ... </details>`.
37
+
validations:
38
+
required: true
39
+
- type: dropdown
40
+
id: versions
41
+
attributes:
42
+
label: "CPython versions tested on:"
43
+
description: >
44
+
If any tested version was not vulnerable, say which in the summary. Only [supported versions](https://devguide.python.org/versions/) accept reports.
45
+
multiple: true
46
+
options:
47
+
- "3.11"
48
+
- "3.12"
49
+
- "3.13"
50
+
- "3.14"
51
+
- "3.15"
52
+
- "3.16"
53
+
- "CPython main branch"
54
+
validations:
55
+
required: true
56
+
- type: textarea
57
+
id: patch
58
+
attributes:
59
+
label: Suggested fix
60
+
description: Ideally, a minimal patch with the mitigation.
61
+
validations:
62
+
required: false
63
+
- type: checkboxes
64
+
id: checklist
65
+
attributes:
66
+
label: Before submitting
67
+
options:
68
+
- label: I have read the security policy and evaluated this report against it.
69
+
required: true
70
+
- label: I have checked that this issue is not already resolved on the `main` branch.
71
+
required: true
72
+
- label: I have verified the factual validity of everything in this report, including any content produced by an LLM.
0 commit comments