Update URLs so link-checker doesn't spew red.

8 files changed, 29 insertions, 29 deletions

diff --git a/doc/cmd.rst b/doc/cmd.rst
index e9d5100..dc70353 100644
--- a/doc/cmd.rst
+++ b/doc/cmd.rst
@@ -113,8 +113,8 @@ in the configuration file.  Options on the command line will not be passed to
 the processes that multiprocessing creates.  Best practice is to use the
 configuration file for all options.
 
-.. _multiprocessing: https://docs.python.org/2/library/multiprocessing.html
-.. _greenlet: http://greenlet.readthedocs.org/en/latest/
+.. _multiprocessing: https://docs.python.org/3/library/multiprocessing.html
+.. _greenlet: http://greenlet.readthedocs.io/en/latest/
 .. _gevent: http://www.gevent.org/
 .. _eventlet: http://eventlet.net/
 
@@ -351,7 +351,7 @@ file decorated to show the status of each line.
 
 Here's a `sample report`__.
 
-__ http://nedbatchelder.com/files/sample_coverage_html/index.html
+__ https://nedbatchelder.com/files/sample_coverage_html/index.html
 
 Lines are highlighted green for executed, red for missing, and gray for
 excluded.  The counts at the top of the file are buttons to turn on and off
diff --git a/doc/config.rst b/doc/config.rst
index 0740ef1..a8005a4 100644
--- a/doc/config.rst
+++ b/doc/config.rst
@@ -113,8 +113,8 @@ libraries in use by the product code.  If your program uses `multiprocessing`_,
 `gevent`_, `greenlet`_, or `eventlet`_, you must name that library in this
 option, or coverage.py will produce very wrong results.
 
-.. _multiprocessing: https://docs.python.org/2/library/multiprocessing.html
-.. _greenlet: http://greenlet.readthedocs.org/en/latest/
+.. _multiprocessing: https://docs.python.org/3/library/multiprocessing.html
+.. _greenlet: http://greenlet.readthedocs.io/en/latest/
 .. _gevent: http://www.gevent.org/
 .. _eventlet: http://eventlet.net/
 
diff --git a/doc/faq.rst b/doc/faq.rst
index ea69aea..ef7e872 100644
--- a/doc/faq.rst
+++ b/doc/faq.rst
@@ -98,7 +98,7 @@ as you should.
 
 It's good, but `it isn't perfect`__.
 
-__ http://nedbatchelder.com/blog/200710/flaws_in_coverage_measurement.html
+__ https://nedbatchelder.com/blog/200710/flaws_in_coverage_measurement.html
 
 
 ..  Other resources
@@ -109,15 +109,15 @@ __ http://nedbatchelder.com/blog/200710/flaws_in_coverage_measurement.html
 
     - `trialcoverage`_ is a plug-in for Twisted trial.
 
-    .. _trialcoverage: http://pypi.python.org/pypi/trialcoverage
+    .. _trialcoverage: https://pypi.python.org/pypi/trialcoverage
 
     - `pytest-coverage`_
 
-    .. _pytest-coverage: http://pypi.python.org/pypi/pytest-coverage
+    .. _pytest-coverage: https://pypi.python.org/pypi/pytest-coverage
 
     - `django-coverage`_ for use with Django.
 
-    .. _django-coverage: http://pypi.python.org/pypi/django-coverage
+    .. _django-coverage: https://pypi.python.org/pypi/django-coverage
 
 
 **Q: Where can I get more help with coverage.py?**
@@ -129,7 +129,7 @@ mailing list.
 
 Bug reports are gladly accepted at the `Bitbucket issue tracker`_.
 
-.. _Bitbucket issue tracker: http://bitbucket.org/ned/coveragepy/issues
+.. _Bitbucket issue tracker: https://bitbucket.org/ned/coveragepy/issues
 
 Announcements of new coverage.py releases are sent to the
 `coveragepy-announce`_ mailing list.
@@ -139,7 +139,7 @@ Announcements of new coverage.py releases are sent to the
 `I can be reached`__ in a number of ways, I'm happy to answer questions about
 using coverage.py.
 
-__  http://nedbatchelder.com/site/aboutned.html
+__  https://nedbatchelder.com/site/aboutned.html
 
 
 History
@@ -150,5 +150,5 @@ Since 2004, `Ned Batchelder`_ has extended and maintained it with the help of
 `many others`_.  The :ref:`change history <changes>` has all the details.
 
 .. _Gareth Rees:    http://garethrees.org/
-.. _Ned Batchelder: http://nedbatchelder.com
-.. _many others:    http://bitbucket.org/ned/coveragepy/src/tip/CONTRIBUTORS.txt
+.. _Ned Batchelder: https://nedbatchelder.com
+.. _many others:    https://bitbucket.org/ned/coveragepy/src/tip/CONTRIBUTORS.txt
diff --git a/doc/howitworks.rst b/doc/howitworks.rst
index 7c20092..764472b 100644
--- a/doc/howitworks.rst
+++ b/doc/howitworks.rst
@@ -56,7 +56,7 @@ file, usually named ``.coverage``.  This is a JSON-based file containing all of
 the recorded file names and line numbers executed.
 
 .. _sys.settrace: https://docs.python.org/3/library/sys.html#sys.settrace
-.. _How C trace functions really work: http://nedbatchelder.com/text/trace-function.html
+.. _How C trace functions really work: https://nedbatchelder.com/text/trace-function.html
 
 
 Analysis
diff --git a/doc/index.rst b/doc/index.rst
index 0d21a71..0d8e752 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -89,7 +89,7 @@ not.
     **This is a pre-release build.  The usual warnings about possible bugs
     apply.** The latest stable version is coverage.py 4.3.4, `described here`_.
 
-.. _described here: http://nedbatchelder.com/code/coverage
+.. _described here: https://nedbatchelder.com/code/coverage
 
 
 Quick start
@@ -137,9 +137,9 @@ Getting started is easy:
         Then visit htmlcov/index.html in your browser, to see a
         `report like this one`_.
 
-.. _coverage.py page on the Python Package Index: http://pypi.python.org/pypi/coverage
-.. _report like this: http://nedbatchelder.com/files/sample_coverage_html/index.html
-.. _report like this one: http://nedbatchelder.com/files/sample_coverage_html_beta/index.html
+.. _coverage.py page on the Python Package Index: https://pypi.python.org/pypi/coverage
+.. _report like this: https://nedbatchelder.com/files/sample_coverage_html/index.html
+.. _report like this one: https://nedbatchelder.com/files/sample_coverage_html_beta/index.html
 
 
 Using coverage.py
@@ -176,14 +176,14 @@ Bug reports are gladly accepted at the `Bitbucket issue tracker`_.
 Bitbucket also hosts the `code repository`_. There is a `mirrored repo`_ on
 GitHub.
 
-.. _Bitbucket issue tracker: http://bitbucket.org/ned/coveragepy/issues
-.. _code repository: http://bitbucket.org/ned/coveragepy
+.. _Bitbucket issue tracker: https://bitbucket.org/ned/coveragepy/issues
+.. _code repository: https://bitbucket.org/ned/coveragepy
 .. _mirrored repo: https://github.com/nedbat/coveragepy
 
 `I can be reached`_ in a number of ways. I'm happy to answer questions about
 using coverage.py.
 
-.. _I can be reached: http://nedbatchelder.com/site/aboutned.html
+.. _I can be reached: https://nedbatchelder.com/site/aboutned.html
 
 
 
diff --git a/doc/install.rst b/doc/install.rst
index 5774d1b..29bc833 100644
--- a/doc/install.rst
+++ b/doc/install.rst
@@ -29,8 +29,8 @@ Installation
 
 .. highlight:: console
 
-.. _coverage_pypi: http://pypi.python.org/pypi/coverage
-.. _setuptools: http://pypi.python.org/pypi/setuptools
+.. _coverage_pypi: https://pypi.python.org/pypi/coverage
+.. _setuptools: https://pypi.python.org/pypi/setuptools
 
 
 You can install coverage.py in the usual ways. The simplest way is with pip::
diff --git a/doc/subprocess.rst b/doc/subprocess.rst
index b9527c8..7236b7e 100644
--- a/doc/subprocess.rst
+++ b/doc/subprocess.rst
@@ -90,4 +90,4 @@ For example if you send SIGTERM to end the sub-process, but your sub-process
 has never registered any SIGTERM handler, then a coverage file won't be
 written.  See the `atexit`_ docs for details of when the handler isn't run.
 
-.. _atexit: https://docs.python.org/2/library/atexit.html
+.. _atexit: https://docs.python.org/3/library/atexit.html
diff --git a/doc/trouble.rst b/doc/trouble.rst
index e74e18c..7534c5c 100644
--- a/doc/trouble.rst
+++ b/doc/trouble.rst
@@ -46,10 +46,10 @@ coverage.py from working properly:
   sys.settrace, then it will conflict with coverage.py, and it won't be
   measured properly.
 
-.. _execv: http://docs.python.org/library/os#os.execl
-.. _sys.settrace: http://docs.python.org/library/sys.html#sys.settrace
-.. _thread: https://docs.python.org/2/library/thread.html
-.. _threading: http://docs.python.org/library/threading.html
+.. _execv: https://docs.python.org/3/library/os.html#os.execl
+.. _sys.settrace: https://docs.python.org/3/library/sys.html#sys.settrace
+.. _thread: https://docs.python.org/3/library/_thread.html
+.. _threading: https://docs.python.org/3/library/threading.html
 .. _issue 43: https://bitbucket.org/ned/coveragepy/issues/43/coverage-measurement-fails-on-code
 
 
@@ -64,7 +64,7 @@ timid=True`` configuration option.
   DecoratorTools fiddles with the trace function.  You  will need to use
   ``--timid``.
 
-.. _DecoratorTools: http://pypi.python.org/pypi/DecoratorTools
+.. _DecoratorTools: https://pypi.python.org/pypi/DecoratorTools
 .. _TurboGears: http://turbogears.org/