Repository navigation
Code still refers to bugs.python.org #91565
Description
The code on main still references bugs.python.org as the location to report bugs rather than https://github.com/python/cpython/issues while the users will be redirected from bugs.python.org it would be preferable to reference the correct URL.
Using an re of "bugs.python.org/?[)\s>]" to try to exclude results that are mentioning past bugs/issues this returns instances of:
.\Doc\README.rst:
133 : `Python bug tracker <https://bugs.python.org>`_.
.\Doc\tools\extensions\pyspecific.py:
57 : # Support for marking up and linking to bugs.python.org issues
.\Doc\whatsnew\2.6.rst:
184 : https://bugs.python.org
.\Doc\whatsnew\2.7.rst:
73 : feature or the issue on https://bugs.python.org in which a change was
.\Lib\locale.py:
1478 : # submit a bug report to the Python bug tracker at http://bugs.python.org/
.\Lib\platform.py:
13 : # Python bug tracker (http://bugs.python.org) and assign them to "lemburg".
.\Lib\test\crashers\README:
11 : failure, as well as a bugs.python.org issue number if it exists. Particularly
.\Lib\test\test_xml_etree.py:
2182 : # reported on bugs.python.org
.\Mac\README.rst:
338 : configure: WARNING: ## Report this to https://bugs.python.org/ ##
.\Python\dtoa.c:
75 : * (http://bugs.python.org). */
.\configure:
5 : # Report bugs to <https://bugs.python.org/>.
270 : $0: https://bugs.python.org/ about your system, including
1918 : Report bugs to <https://bugs.python.org/>.
2141 : ## Report this to https://bugs.python.org/ ##
25522 : Report bugs to <https://bugs.python.org/>."
The Doc\whatsnew entries could safely be ignored in my opinion, the platform, readme and configure items only need simple substitutions but the .\Doc\tools\extensions\pyspecific.py will require more work as it maps between bpo and bugs.
I would suggest that any changes to the platform, readme and configure items could be considered for backporting to versions still in maintenance.
Linked PRs
- gh-91565 Simple changes to reflect new bug reporting location. #91568
- gh-91565: Update issue tracker URL in error message. #117450
- [3.12] gh-91565: Update issue tracker URL in error message. (GH-117450) #117497
- [3.12] gh-91565: Replace bugs.python.org links with Devguide/GitHub ones (GH-91568) #117890
Activity
Simple changes to reflect new bug reporting location. Does not addres…
GadgetSteve commentedon Apr 15, 2022
The simple changes are done in the commit above 265a778 but changes to
Doc/tools/extensions/pyspecific.pyto reference GitHub result in problems as the BPO issue numbers do not map directly to the GitHub issue numbers. Separating that to an new issue #91567 as it will need some discussion on how to get it to work correctly. Creating a PR for the "simple" substitutions.Reword links to issues to make it clearer they are to the devguide. p…
Wording changes to configure overidden by autoconf. pythongh-91565
Corrected lemburg to malemburg in Lib/platform.py. pythongh-91565
Changes to configure.ac to correct wording of bug tracker reference i…
gh-91565: Replace bugs.python.org links with Devguide/GitHub ones (GH…
Squashed commit of the following:
Squashed commit of the following:
encukou commentedon Apr 2, 2024
Hm, turns out there's one more.
gh-91565: Update issue tracker URL in error message. (#117450)
pythongh-91565: Update issue tracker URL in error message. (pythonGH-…
[3.12] gh-91565: Update issue tracker URL in error message. (GH-117450)…
ezio-melotti commentedon Apr 3, 2024
This should now be fixed.
@encukou, do you want to backport #91568 to 3.12?
pythongh-91565: Replace bugs.python.org links with Devguide/GitHub on…
[3.12] gh-91565: Replace bugs.python.org links with Devguide/GitHub o…
encukou commentedon Apr 15, 2024
Yes; I just did so. Sorry for the delay!
GadgetSteve commentedon Apr 15, 2024
Thanks all!
pythongh-91565: Replace bugs.python.org links with Devguide/GitHub on…
pythongh-91565: Update issue tracker URL in error message. (python#11…