@@ -32,38 +32,39 @@ though it may take a while to be processed.
3232Using the Python issue tracker
3333==============================
3434
35- Bug reports for Python itself should be submitted via the Python Bug Tracker
36- (https://bugs.python.org/). The bug tracker offers a Web form which allows
37- pertinent information to be entered and submitted to the developers.
35+ Issue reports for Python itself should be submitted via the GitHub issues
36+ tracker (https://github.com/python/cpython/issues).
37+ The GitHub issues tracker offers a web form which allows pertinent information
38+ to be entered and submitted to the developers.
3839
3940The first step in filing a report is to determine whether the problem has
4041already been reported. The advantage in doing so, aside from saving the
41- developers time, is that you learn what has been done to fix it; it may be that
42+ developers' time, is that you learn what has been done to fix it; it may be that
4243the problem has already been fixed for the next release, or additional
4344information is needed (in which case you are welcome to provide it if you can!).
44- To do this, search the bug database using the search box on the top of the page.
45+ To do this, search the tracker using the search box at the top of the page.
4546
46- If the problem you're reporting is not already in the bug tracker, go back to
47- the Python Bug Tracker and log in. If you don't already have a tracker account,
48- select the "Register" link or, if you use OpenID, one of the OpenID provider
49- logos in the sidebar. It is not possible to submit a bug report anonymously.
47+ If the problem you're reporting is not already in the list, log in to GitHub.
48+ If you don't already have a GitHub account, create a new account using the
49+ "Sign up" link.
50+ It is not possible to submit a bug report anonymously.
5051
51- Being now logged in, you can submit a bug. Select the "Create New" link in the
52- sidebar to open the bug reporting form .
52+ Being now logged in, you can submit an issue.
53+ Click on the "New issue" button in the top bar to report a new issue .
5354
54- The submission form has a number of fields. For the "Title" field, enter a
55- * very * short description of the problem; less than ten words is good. In the
56- "Type " field, select the type of your problem; also select the "Component" and
57- "Versions" to which the bug relates .
55+ The submission form has two fields, "Title" and "Comment".
56+
57+ For the "Title " field, enter a * very * short description of the problem;
58+ less than ten words is good .
5859
5960In the "Comment" field, describe the problem in detail, including what you
6061expected to happen and what did happen. Be sure to include whether any
6162extension modules were involved, and what hardware and software platform you
6263were using (including version information as appropriate).
6364
64- Each bug report will be assigned to a developer who will determine what needs to
65- be done to correct the problem. You will receive an update each time action is
66- taken on the bug .
65+ Each issue report will be reviewed by a developer who will determine what needs to
66+ be done to correct the problem. You will receive an update each time an action is
67+ taken on the issue .
6768
6869
6970.. seealso ::
@@ -87,6 +88,6 @@ patching Python in the `Python Developer's Guide`_. If you have questions,
8788the `core-mentorship mailing list `_ is a friendly place to get answers to
8889any and all questions pertaining to the process of fixing issues in Python.
8990
90- .. _Documentation bugs : https://bugs. python.org/issue?@filter=status&@filter=components&components=4&status=1&@columns=id,activity,title,status&@sort=-activity
91+ .. _Documentation bugs : https://github.com/ python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs
9192.. _Python Developer's Guide : https://devguide.python.org/
9293.. _core-mentorship mailing list : https://mail.python.org/mailman3/lists/core-mentorship.python.org/
0 commit comments