Use HTTPS protocol instead of HTTP (python#383)

suriyaa · brettcannon · commit eedc485da182 · 2018-06-08T10:39:23.000-07:00
diff --git a/LICENSE b/LICENSE
@@ -113,4 +113,4 @@ Affirmer's express Statement of Purpose.
   CC0 or use of the Work.
 
 For more information, please see
-<http://creativecommons.org/publicdomain/zero/1.0/>
+<https://creativecommons.org/publicdomain/zero/1.0/>
diff --git a/buildworker.rst b/buildworker.rst
@@ -58,7 +58,7 @@ Setting up the buildbot worker
 Conventional always-on machines
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-You need a recent version of the `buildbot <http://buildbot.net/>`_ software,
+You need a recent version of the `buildbot <https://buildbot.net/>`_ software,
 and you will probably want a separate 'buildbot' user to run the buildbot
 software.  You may also want to set the buildbot up using a virtual
 environment, depending on how you manage your system.  We won't cover how to that
diff --git a/clang.rst b/clang.rst
@@ -38,7 +38,7 @@ flags are passed through ``CFLAGS`` and ``CXXFLAGS``, and sometimes through
 ``CC`` and ``CXX`` (in addition to the compiler).
 
 A complete list of sanitizers can be found at `Controlling Code Generation
-<http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation>`_.
+<https://clang.llvm.org/docs/UsersManual.html#controlling-code-generation>`_.
 
 .. note::
 
@@ -66,9 +66,9 @@ Download, Build and Install
 Perform the following to download, build and install the Clang/LLVM 3.4. ::
 
     # Download
-    wget http://llvm.org/releases/3.4/llvm-3.4.src.tar.gz
-    wget http://llvm.org/releases/3.4/clang-3.4.src.tar.gz
-    wget http://llvm.org/releases/3.4/compiler-rt-3.4.src.tar.gz
+    wget https://llvm.org/releases/3.4/llvm-3.4.src.tar.gz
+    wget https://llvm.org/releases/3.4/clang-3.4.src.tar.gz
+    wget https://llvm.org/releases/3.4/compiler-rt-3.4.src.tar.gz
 
     # LLVM
     tar xvf llvm-3.4.src.tar.gz
@@ -351,4 +351,4 @@ Or, you could ignore the entire file with::
 Unfortunately, you won't know what to blacklist until you run the sanitizer.
 
 The documentation is available at `Sanitizer special case list
-<http://clang.llvm.org/docs/SanitizerSpecialCaseList.html>`_.
+<https://clang.llvm.org/docs/SanitizerSpecialCaseList.html>`_.
diff --git a/communication.rst b/communication.rst
@@ -57,7 +57,7 @@ mailing list is the place to discuss and work on improvements to the CPython
 core development workflow.
 
 A complete list of Python mailing lists can be found at https://mail.python.org.
-Most lists are also mirrored at `GMANE <http://gmane.org>`_ and can be read and
+Most lists are also mirrored at `GMANE <https://gmane.org>`_ and can be read and
 posted to in various ways, including via web browsers, NNTP newsreaders, and
 RSS feed readers.
 
@@ -87,7 +87,7 @@ Some core developers enjoy spending time on IRC discussing various issues
 regarding Python's development in the ``#python-dev`` channel on
 ``irc.freenode.net``. This is not a place to ask for help with Python, but to
 discuss issues related to Python's own development.  You can use Freenode's
-`Web interface <http://webchat.freenode.net/>`_ if you don't have an IRC
+`Web interface <https://webchat.freenode.net/>`_ if you don't have an IRC
 client.
 
 
diff --git a/compiler.rst b/compiler.rst
@@ -575,7 +575,7 @@ References
    213--227, 1997.
 
 .. _The Zephyr Abstract Syntax Description Language.:
-   http://www.cs.princeton.edu/research/techreps/TR-554-97
+   https://www.cs.princeton.edu/research/techreps/TR-554-97
 
 .. [#skip-peephole] Skip Montanaro's Peephole Optimizer Paper
    (https://drive.google.com/open?id=0B2InO7qBBGRXQXlDM3FVdWZxQWc)
diff --git a/coverage.rst b/coverage.rst
@@ -210,7 +210,7 @@ following from your CPython clone::
 This will give you the most complete coverage possible for CPython's standard
 library.
 
-.. _coverage.py: http://coverage.readthedocs.io/en/latest/
+.. _coverage.py: https://coverage.readthedocs.io/en/latest/
 
 
 .. _coverage_by_regrtest:
@@ -276,5 +276,5 @@ about 20 to 30 minutes on a modern computer.
     Multiple test jobs may not work properly. C coverage reporting has only
     been tested with a single test process.
 
-.. _gcov: http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
+.. _gcov: https://gcc.gnu.org/onlinedocs/gcc/Gcov.html
 .. _lcov: http://ltp.sourceforge.net/coverage/lcov.php
diff --git a/exploring.rst b/exploring.rst
@@ -82,7 +82,7 @@ building your understanding of both the 2.x and 3.x versions of CPython:
 
 .. _Python's Innards Series: https://tech.blog.aknin.name/category/my-projects/pythons-innards/
 
-.. _Eli Bendersky's Python Internals: http://eli.thegreenplace.net/tag/python-internals
+.. _Eli Bendersky's Python Internals: https://eli.thegreenplace.net/tag/python-internals
 
 .. _A guide from parser to objects, observed using Eclipse: https://docs.google.com/document/d/1nzNN1jeNCC_bg1LADCvtTuGKvcyMskV1w8Ad2iLlwoI/
 
diff --git a/gdb.rst b/gdb.rst
@@ -20,7 +20,7 @@ gdb 7 and later
 ---------------
 
 In gdb 7, support for `extending gdb with Python
-<http://sourceware.org/gdb/current/onlinedocs/gdb/Python.html#Python>`_ was
+<https://sourceware.org/gdb/current/onlinedocs/gdb/Python.html#Python>`_ was
 added. When CPython is built you will notice a ``python-gdb.py`` file in the
 root directory of your checkout. Read the module docstring for details on how
 to use the file to enhance gdb for easier debugging of a CPython process.
diff --git a/help.rst b/help.rst
@@ -23,7 +23,7 @@ questions about developing for Python.  Just remember that ``#python-dev``
 is for questions involving the development *of* Python whereas ``#python``
 is for questions concerning development *with* Python.
 
-.. _freenode: http://freenode.net/
+.. _freenode: https://freenode.net/
 
 
 Core Mentorship
diff --git a/langchanges.rst b/langchanges.rst
@@ -93,5 +93,5 @@ For some examples on language changes that were accepted please read
 .. _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
-.. _Justifying Python Language Changes: http://www.curiousefficiency.org/posts/2011/02/justifying-python-language-changes.html
+.. _Status Quo Wins a Stalemate: https://www.curiousefficiency.org/posts/2011/02/status-quo-wins-stalemate.html
+.. _Justifying Python Language Changes: https://www.curiousefficiency.org/posts/2011/02/justifying-python-language-changes.html
diff --git a/motivations.rst b/motivations.rst
@@ -101,8 +101,8 @@ participating in the CPython core development process:
 
 .. topic:: Nick Coghlan (Australia)
 
-   * Personal site: `Curious Efficiency <http://www.curiousefficiency.org/>`_
-   * `Extended bio <http://www.curiousefficiency.org/pages/about>`__
+   * Personal site: `Curious Efficiency <https://www.curiousefficiency.org/>`_
+   * `Extended bio <https://www.curiousefficiency.org/pages/about>`__
    * `Tritium <https://www.tritium.com.au/>`__ (Software Developer)
    * Python Software Foundation (Fellow, Packaging Working Group)
 
diff --git a/stdlibchanges.rst b/stdlibchanges.rst
@@ -47,7 +47,7 @@ Through your public sharing of your code in order to gauge community support
 for it you at least can know that others will come across it who may find it
 useful.
 
-.. _Python Cookbook: http://code.activestate.com/recipes/langs/python/
+.. _Python Cookbook: https://code.activestate.com/recipes/langs/python/
 
 
 Adding a new module
diff --git a/tracker.rst b/tracker.rst
@@ -41,7 +41,7 @@ Reporting an issue
 If the problem you're reporting is not already in the `issue tracker`_, you
 need to log in by entering your user and password in the form on the left.
 If you don't already have a tracker account, select the "Register" link or,
-if you use `OpenID <http://openid.net>`_, one of the OpenID provider logos in
+if you use `OpenID <https://openid.net>`_, one of the OpenID provider logos in
 the sidebar.
 
 It is not possible to submit a bug report anonymously.
