Use https url for bpo (pythonGH-248)

Mariatta · web-flow · commit 8b9e729e438e · 2017-07-30T20:06:16.000-07:00
diff --git a/communication.rst b/communication.rst
@@ -61,7 +61,7 @@ Most lists are also mirrored at http://news.gmane.org/ and can be read and
 posted to in various ways, including via web browsers, NNTP newsreaders, and
 RSS feed readers.
 
-.. _issue tracker: http://bugs.python.org
+.. _issue tracker: https://bugs.python.org
 .. _new-bugs-announce: https://mail.python.org/mailman/listinfo/new-bugs-announce
 .. _python-bugs-list: https://mail.python.org/mailman/listinfo/python-bugs-list
 .. _python-checkins: https://mail.python.org/mailman/listinfo/python-checkins
diff --git a/compiler.rst b/compiler.rst
@@ -535,4 +535,4 @@ References
    (http://bytecodehacks.sourceforge.net/bch-docs/bch/index.html)
 
 .. [#CALL_ATTR] CALL_ATTR opcode
-   (http://bugs.python.org/issue709744)
+   (https://bugs.python.org/issue709744)
diff --git a/coverage.rst b/coverage.rst
@@ -232,7 +232,7 @@ you want the coverage data to end up it will go somewhere you don't expect.
     If you are running coverage over the entire test suite, make sure to
     add ``-x test_importlib test_runpy test_trace`` to exclude those tests as
     they trigger exceptions during coverage; see
-    http://bugs.python.org/issue10541 and http://bugs.python.org/issue10991.
+    https://bugs.python.org/issue10541 and https://bugs.python.org/issue10991.
 
 Once the tests are done you will find the directory you specified contains
 files for each executed module along with which lines were executed how many
@@ -246,7 +246,7 @@ Once you have increased coverage, you need to create an issue on the
 issue set the "Components" to "Test" and "Versions" to the version of Python you
 worked on (i.e., the in-development version).
 
-.. _issue tracker: http://bugs.python.org
+.. _issue tracker: https://bugs.python.org
 
 
 Measuring coverage of C code with gcov and lcov
diff --git a/fixingissues.rst b/fixingissues.rst
@@ -20,6 +20,6 @@ discussion to help bring it to a close). Regardless of why the issue is open,
 you can also always provide useful comments if you do attempt a fix, successful
 or not.
 
-.. _"easy" issues: http://bugs.python.org/issue?status=1&@sort=-activity&@dispname=Easy%20issues&@startwith=0&@filter=&@group=priority&@columns=id,activity,title,creator,status&keywords=6&@action=search&@pagesize=50
+.. _"easy" issues: https://bugs.python.org/issue?status=1&@sort=-activity&@dispname=Easy%20issues&@startwith=0&@filter=&@group=priority&@columns=id,activity,title,creator,status&keywords=6&@action=search&@pagesize=50
 
 .. TODO: add something about no active core developer for the area?
diff --git a/grammar.rst b/grammar.rst
@@ -20,7 +20,7 @@ Rationale
 ---------
 
 People are getting this wrong all the time; it took well over a
-year before someone `noticed <http://bugs.python.org/issue676521>`_
+year before someone `noticed <https://bugs.python.org/issue676521>`_
 that adding the floor division
 operator (//) broke the parser module.
 
diff --git a/help.rst b/help.rst
@@ -66,4 +66,4 @@ you detail which conditions triggered it (including the OS name and version,
 and what you were trying to do), as well as the exact error message you
 encountered.
 
-.. _issue tracker: http://bugs.python.org
+.. _issue tracker: https://bugs.python.org
diff --git a/langchanges.rst b/langchanges.rst
@@ -90,7 +90,7 @@ For some examples on language changes that were accepted please read
 `Justifying Python Language Changes`_.
 
 .. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas
-.. _issue tracker: http://bugs.python.org
+.. _issue tracker: https://bugs.python.org
 .. _PEP Index: https://www.python.org/dev/peps/
 .. _draft PEP: https://www.python.org/dev/peps/pep-0001/
 .. _Status Quo Wins a Stalemate: http://www.curiousefficiency.org/posts/2011/02/status-quo-wins-stalemate.html
diff --git a/motivations.rst b/motivations.rst
@@ -220,7 +220,7 @@ their contributions to be funded directly by the community, rather than relying
 on institutional sponsors allowing them to spend some or all of their work
 time contributing to CPython development.
 
-.. _issue metrics: http://bugs.python.org/issue?@template=stats
+.. _issue metrics: https://bugs.python.org/issue?@template=stats
 .. _OpenHub: https://www.openhub.net/p/python/contributors
 .. _core mentorship program: https://www.python.org/dev/core-mentorship/
 .. _internships: https://www.gnome.org/outreachy/
diff --git a/silencewarnings.rst b/silencewarnings.rst
@@ -15,4 +15,4 @@ If you decide to tackle a warning you have found, open an issue on the `issue
 tracker`_ (if one has not already been opened) and say you are going to try and
 tackle the issue, and then proceed to fix the issue.
 
-.. _issue tracker: http://bugs.python.org
+.. _issue tracker: https://bugs.python.org
diff --git a/stdlibchanges.rst b/stdlibchanges.rst
@@ -11,7 +11,7 @@ module.
 Changes to pre-existing code is not covered as that is considered a bugfix and
 thus is treated as a bug that should be filed on the `issue tracker`_.
 
-.. _issue tracker: http://bugs.python.org/
+.. _issue tracker: https://bugs.python.org/
 
 
 Adding to a pre-existing module
diff --git a/tracker.rst b/tracker.rst
@@ -193,7 +193,7 @@ instructions on the `Tracker Development`_ page.
 
 .. seealso::
 
-   `The Python issue tracker <http://bugs.python.org/>`_
+   `The Python issue tracker <https://bugs.python.org/>`_
       Where to report issues about Python.
 
    `The New-bugs-announce mailing list <https://mail.python.org/mailman/listinfo/new-bugs-announce>`_
@@ -212,7 +212,7 @@ instructions on the `Tracker Development`_ page.
       Discussions about the bug tracker.
 
 
-.. _issue tracker: http://bugs.python.org/
+.. _issue tracker: https://bugs.python.org/
 .. _meta tracker: http://psf.upfronthosting.co.za/roundup/meta/
-.. _advanced search: http://bugs.python.org/issue?@template=search
+.. _advanced search: https://bugs.python.org/issue?@template=search
 .. _Tracker Development: https://wiki.python.org/moin/TrackerDevelopment
