mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-10-22 14:42:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

gh-91423: Remove bugs.python.org from bugs.rst (GH-91425)

Browse source 
* Remove bugs.python.org from bugs.rst

* Update bugs.rst to the github issue tracker

* reflow

* Fix a typo and rephrase a sentence.

Co-authored-by: Inada Naoki <songofacandy@gmail.com>
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
This commit is contained in:
roy reznik 2022-04-11 18:10:34 +03:00 • committed by GitHub
parent f6e43e834c
commit df81d2892e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 20 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

39
Doc/bugs.rst
View file

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