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

14 files changed, 83 insertions, 83 deletions

diff --git a/CHANGES.rst b/CHANGES.rst
index 0a2a521..9556bf0 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -1298,7 +1298,7 @@ Version 3.5.3 --- 2012-09-29
 .. _issue 194: https://bitbucket.org/ned/coveragepy/issues/194/filelocatorrelative_filename-could-mangle
 .. _issue 195: https://bitbucket.org/ned/coveragepy/issues/195/pyo-file-handling-in-codeunit
 .. _issue 197: https://bitbucket.org/ned/coveragepy/issues/197/line-numbers-in-html-report-do-not-align
-.. _tox: http://tox.readthedocs.org/
+.. _tox: http://tox.readthedocs.io/
 
 
 .. _changes_352:
@@ -1394,12 +1394,12 @@ Version 3.5.1b1 --- 2011-08-28
   into running some coverage.py code before anything else in the process.
   See the coverage/fullcoverage directory if you are interested.
 
-.. _issue 17: http://bitbucket.org/ned/coveragepy/issues/17/support-combining-coverage-data-from
-.. _issue 122: http://bitbucket.org/ned/coveragepy/issues/122/for-else-always-reports-missing-branch
-.. _issue 124: http://bitbucket.org/ned/coveragepy/issues/124/no-arbitrary-unicode-in-html-reports-in
-.. _issue 128: http://bitbucket.org/ned/coveragepy/issues/128/branch-coverage-of-with-statement-in-27
-.. _issue 138: http://bitbucket.org/ned/coveragepy/issues/138/include-should-take-precedence-over-is
-.. _issue 144: http://bitbucket.org/ned/coveragepy/issues/144/failure-generating-html-output-for
+.. _issue 17: https://bitbucket.org/ned/coveragepy/issues/17/support-combining-coverage-data-from
+.. _issue 122: https://bitbucket.org/ned/coveragepy/issues/122/for-else-always-reports-missing-branch
+.. _issue 124: https://bitbucket.org/ned/coveragepy/issues/124/no-arbitrary-unicode-in-html-reports-in
+.. _issue 128: https://bitbucket.org/ned/coveragepy/issues/128/branch-coverage-of-with-statement-in-27
+.. _issue 138: https://bitbucket.org/ned/coveragepy/issues/138/include-should-take-precedence-over-is
+.. _issue 144: https://bitbucket.org/ned/coveragepy/issues/144/failure-generating-html-output-for
 
 
 .. _changes_35:
@@ -1482,7 +1482,7 @@ Version 3.5b1 --- 2011-06-05
   Brett Cannon.
 
 .. _issue 80: https://bitbucket.org/ned/coveragepy/issues/80/is-there-a-duck-typing-way-to-know-we-cant
-.. _issue 93: http://bitbucket.org/ned/coveragepy/issues/93/copying-a-mock-object-breaks-coverage
+.. _issue 93: https://bitbucket.org/ned/coveragepy/issues/93/copying-a-mock-object-breaks-coverage
 .. _issue 95: https://bitbucket.org/ned/coveragepy/issues/95/run-subcommand-should-take-a-module-name
 .. _issue 104: https://bitbucket.org/ned/coveragepy/issues/104/explicitly-close-files
 .. _issue 107: https://bitbucket.org/ned/coveragepy/issues/107/codeparser-not-opening-source-files-with
@@ -1502,7 +1502,7 @@ Version 3.4 --- 2010-09-19
 - Programs that exited with ``sys.exit()`` with no argument weren't handled
   properly, producing a coverage.py stack trace.  That is now fixed.
 
-.. _issue 88: http://bitbucket.org/ned/coveragepy/issues/88/xml-report-lists-packages-in-random-order
+.. _issue 88: https://bitbucket.org/ned/coveragepy/issues/88/xml-report-lists-packages-in-random-order
 
 
 Version 3.4b2 --- 2010-09-06
@@ -1527,12 +1527,12 @@ Version 3.4b2 --- 2010-09-06
   would report no coverage for the `run` method.  This is now fixed, closing
   `issue 85`_.
 
-.. _issue 16: http://bitbucket.org/ned/coveragepy/issues/16/allow-configuration-of-accuracy-of-percentage-totals
-.. _issue 41: http://bitbucket.org/ned/coveragepy/issues/41/report-says-100-when-it-isnt-quite-there
-.. _issue 65: http://bitbucket.org/ned/coveragepy/issues/65/branch-option-not-reported-in-cobertura
-.. _issue 70: http://bitbucket.org/ned/coveragepy/issues/70/text-report-and-html-report-disagree-on-coverage
-.. _issue 81: http://bitbucket.org/ned/coveragepy/issues/81/xml-report-does-not-have-condition-coverage-attribute-for-lines-with-a
-.. _issue 85: http://bitbucket.org/ned/coveragepy/issues/85/threadrun-isnt-measured
+.. _issue 16: https://bitbucket.org/ned/coveragepy/issues/16/allow-configuration-of-accuracy-of-percentage-totals
+.. _issue 41: https://bitbucket.org/ned/coveragepy/issues/41/report-says-100-when-it-isnt-quite-there
+.. _issue 65: https://bitbucket.org/ned/coveragepy/issues/65/branch-option-not-reported-in-cobertura
+.. _issue 70: https://bitbucket.org/ned/coveragepy/issues/70/text-report-and-html-report-disagree-on-coverage
+.. _issue 81: https://bitbucket.org/ned/coveragepy/issues/81/xml-report-does-not-have-condition-coverage-attribute-for-lines-with-a
+.. _issue 85: https://bitbucket.org/ned/coveragepy/issues/85/threadrun-isnt-measured
 
 
 Version 3.4b1 --- 2010-08-21
@@ -1608,17 +1608,17 @@ Version 3.4b1 --- 2010-08-21
 - Asking for an HTML report with no files now shows a nice error message rather
   than a cryptic failure ('int' object is unsubscriptable). Fixes `issue 59`_.
 
-.. _issue 1:  http://bitbucket.org/ned/coveragepy/issues/1/empty-__init__py-files-are-reported-as-1-executable
-.. _issue 34: http://bitbucket.org/ned/coveragepy/issues/34/enhanced-omit-globbing-handling
-.. _issue 36: http://bitbucket.org/ned/coveragepy/issues/36/provide-regex-style-omit
-.. _issue 46: http://bitbucket.org/ned/coveragepy/issues/46
-.. _issue 53: http://bitbucket.org/ned/coveragepy/issues/53
-.. _issue 52: http://bitbucket.org/ned/coveragepy/issues/52/doctesttestfile-confuses-source-detection
-.. _issue 56: http://bitbucket.org/ned/coveragepy/issues/56
-.. _issue 61: http://bitbucket.org/ned/coveragepy/issues/61/annotate-i-doesnt-work
-.. _issue 62: http://bitbucket.org/ned/coveragepy/issues/62
-.. _issue 59: http://bitbucket.org/ned/coveragepy/issues/59/html-report-fails-with-int-object-is
-.. _issue 82: http://bitbucket.org/ned/coveragepy/issues/82/tokenerror-when-generating-html-report
+.. _issue 1:  https://bitbucket.org/ned/coveragepy/issues/1/empty-__init__py-files-are-reported-as-1-executable
+.. _issue 34: https://bitbucket.org/ned/coveragepy/issues/34/enhanced-omit-globbing-handling
+.. _issue 36: https://bitbucket.org/ned/coveragepy/issues/36/provide-regex-style-omit
+.. _issue 46: https://bitbucket.org/ned/coveragepy/issues/46
+.. _issue 53: https://bitbucket.org/ned/coveragepy/issues/53
+.. _issue 52: https://bitbucket.org/ned/coveragepy/issues/52/doctesttestfile-confuses-source-detection
+.. _issue 56: https://bitbucket.org/ned/coveragepy/issues/56
+.. _issue 61: https://bitbucket.org/ned/coveragepy/issues/61/annotate-i-doesnt-work
+.. _issue 62: https://bitbucket.org/ned/coveragepy/issues/62
+.. _issue 59: https://bitbucket.org/ned/coveragepy/issues/59/html-report-fails-with-int-object-is
+.. _issue 82: https://bitbucket.org/ned/coveragepy/issues/82/tokenerror-when-generating-html-report
 
 
 .. _changes_331:
@@ -1632,8 +1632,8 @@ Version 3.3.1 --- 2010-03-06
 - When running your code with "coverage run", if you call `sys.exit()`,
   coverage.py will exit with that status code, fixing `issue 50`_.
 
-.. _issue 49: http://bitbucket.org/ned/coveragepy/issues/49
-.. _issue 50: http://bitbucket.org/ned/coveragepy/issues/50
+.. _issue 49: https://bitbucket.org/ned/coveragepy/issues/49
+.. _issue 50: https://bitbucket.org/ned/coveragepy/issues/50
 
 
 .. _changes_33:
@@ -1672,9 +1672,9 @@ Version 3.3 --- 2010-02-24
 
 - Added an AUTHORS.txt file.
 
-.. _issue 39: http://bitbucket.org/ned/coveragepy/issues/39
-.. _issue 40: http://bitbucket.org/ned/coveragepy/issues/40
-.. _issue 47: http://bitbucket.org/ned/coveragepy/issues/47
+.. _issue 39: https://bitbucket.org/ned/coveragepy/issues/39
+.. _issue 40: https://bitbucket.org/ned/coveragepy/issues/40
+.. _issue 47: https://bitbucket.org/ned/coveragepy/issues/47
 
 
 .. _changes_32:
@@ -1713,7 +1713,7 @@ Version 3.2b3 --- 2009-11-23
 - The table of contents in the HTML report is now sortable: click the headers
   on any column.  Thanks, `Chris Adams`_.
 
-.. _Chris Adams: http://improbable.org/chris/
+.. _Chris Adams: http://chris.improbable.org
 
 
 Version 3.2b2 --- 2009-11-19
@@ -1732,12 +1732,12 @@ Version 3.2b2 --- 2009-11-19
 - The --omit option now works much better than before, fixing `issue 14`_ and
   `issue 33`_.  Thanks, Danek Duvall.
 
-.. _issue 14: http://bitbucket.org/ned/coveragepy/issues/14
-.. _issue 30: http://bitbucket.org/ned/coveragepy/issues/30
-.. _issue 31: http://bitbucket.org/ned/coveragepy/issues/31
-.. _issue 32: http://bitbucket.org/ned/coveragepy/issues/32
-.. _issue 33: http://bitbucket.org/ned/coveragepy/issues/33
-.. _issue 35: http://bitbucket.org/ned/coveragepy/issues/35
+.. _issue 14: https://bitbucket.org/ned/coveragepy/issues/14
+.. _issue 30: https://bitbucket.org/ned/coveragepy/issues/30
+.. _issue 31: https://bitbucket.org/ned/coveragepy/issues/31
+.. _issue 32: https://bitbucket.org/ned/coveragepy/issues/32
+.. _issue 33: https://bitbucket.org/ned/coveragepy/issues/33
+.. _issue 35: https://bitbucket.org/ned/coveragepy/issues/35
 
 
 Version 3.2b1 --- 2009-11-10
@@ -1752,7 +1752,7 @@ Version 3.2b1 --- 2009-11-10
 - Some exceptions reported by the command line interface have been cleaned up
   so that tracebacks inside coverage.py aren't shown.  Fixes `issue 23`_.
 
-.. _issue 23: http://bitbucket.org/ned/coveragepy/issues/23
+.. _issue 23: https://bitbucket.org/ned/coveragepy/issues/23
 
 
 .. _changes_31:
@@ -1763,7 +1763,7 @@ Version 3.1 --- 2009-10-04
 - Source code can now be read from eggs.  Thanks, Ross Lawley.  Fixes
   `issue 25`_.
 
-.. _issue 25: http://bitbucket.org/ned/coveragepy/issues/25
+.. _issue 25: https://bitbucket.org/ned/coveragepy/issues/25
 
 
 Version 3.1b1 --- 2009-09-27
@@ -1793,10 +1793,10 @@ Version 3.1b1 --- 2009-09-27
 - Added a "coverage debug" command for getting diagnostic information about the
   coverage.py installation.
 
-.. _issue 11: http://bitbucket.org/ned/coveragepy/issues/11
-.. _issue 12: http://bitbucket.org/ned/coveragepy/issues/12
-.. _issue 13: http://bitbucket.org/ned/coveragepy/issues/13
-.. _issue 24: http://bitbucket.org/ned/coveragepy/issues/24
+.. _issue 11: https://bitbucket.org/ned/coveragepy/issues/11
+.. _issue 12: https://bitbucket.org/ned/coveragepy/issues/12
+.. _issue 13: https://bitbucket.org/ned/coveragepy/issues/13
+.. _issue 24: https://bitbucket.org/ned/coveragepy/issues/24
 
 
 .. _changes_301:
@@ -1821,9 +1821,9 @@ Version 3.0.1 --- 2009-07-07
   mode just like Python does.  This lets it run Windows files on Mac, for
   example.
 
-.. _issue 9: http://bitbucket.org/ned/coveragepy/issues/9
-.. _issue 10: http://bitbucket.org/ned/coveragepy/issues/10
-.. _issue 8: http://bitbucket.org/ned/coveragepy/issues/8
+.. _issue 9: https://bitbucket.org/ned/coveragepy/issues/9
+.. _issue 10: https://bitbucket.org/ned/coveragepy/issues/10
+.. _issue 8: https://bitbucket.org/ned/coveragepy/issues/8
 
 
 .. _changes_30:
@@ -1839,7 +1839,7 @@ Version 3.0 --- 2009-06-13
 
 - Nested modules now get a proper flat_rootname.  Thanks, Christian Heimes.
 
-.. _issue 6: http://bitbucket.org/ned/coveragepy/issues/6
+.. _issue 6: https://bitbucket.org/ned/coveragepy/issues/6
 
 
 Version 3.0b3 --- 2009-05-16
diff --git a/README.rst b/README.rst
index 162a116..fd25f1b 100644
--- a/README.rst
+++ b/README.rst
@@ -29,7 +29,7 @@ Documentation is on `Read the Docs`_.  Code repository and issue tracker are on
 `Bitbucket`_, with a mirrored repository on `GitHub`_.
 
 .. _Read the Docs: http://coverage.readthedocs.io
-.. _Bitbucket: http://bitbucket.org/ned/coveragepy
+.. _Bitbucket: https://bitbucket.org/ned/coveragepy
 .. _GitHub: https://github.com/nedbat/coveragepy
 
 
diff --git a/coverage/__init__.py b/coverage/__init__.py
index d9a1393..63f488f 100644
--- a/coverage/__init__.py
+++ b/coverage/__init__.py
@@ -4,7 +4,7 @@
 """Code coverage measurement for Python.
 
 Ned Batchelder
-http://nedbatchelder.com/code/coverage
+https://nedbatchelder.com/code/coverage
 
 """
 
diff --git a/coverage/ctracer/tracer.c b/coverage/ctracer/tracer.c
index 095df11..625a45a 100644
--- a/coverage/ctracer/tracer.c
+++ b/coverage/ctracer/tracer.c
@@ -812,7 +812,7 @@ CTracer_handle_exception(CTracer *self, PyFrameObject *frame)
         the bug will be fixed everywhere coverage.py is supported, and we can
         remove this missing-return detection.
 
-        More about this fix: http://nedbatchelder.com/blog/200907/a_nasty_little_bug.html
+        More about this fix: https://nedbatchelder.com/blog/200907/a_nasty_little_bug.html
     */
     STATS( self->stats.exceptions++; )
     self->last_exc_back = frame->f_back;
@@ -989,7 +989,7 @@ CTracer_call(CTracer *self, PyObject *args, PyObject *kwds)
        the new trace function before it has a chance to get called.  To
        understand why, there are three internal values to track: frame.f_trace,
        c_tracefunc, and c_traceobj.  They are explained here:
-       http://nedbatchelder.com/text/trace-function.html
+       https://nedbatchelder.com/text/trace-function.html
 
        Without the conditional on PyTrace_CALL, this is what happens:
 
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/
 
 
diff --git a/howto.txt b/howto.txt
index 3044886..ae85b76 100644
--- a/howto.txt
+++ b/howto.txt
@@ -58,7 +58,7 @@
 - Update PyPi:
     - upload kits:
         - $ make kit_upload
-    - Visit http://pypi.python.org/pypi?:action=pkg_edit&name=coverage :
+    - Visit https://pypi.python.org/pypi?:action=pkg_edit&name=coverage :
         - show/hide the proper versions.
 - Tag the tree
     - hg tag -m "Coverage 3.0.1" coverage-3.0.1
diff --git a/tests/test_oddball.py b/tests/test_oddball.py
index b54f4ef..aa2f333 100644
--- a/tests/test_oddball.py
+++ b/tests/test_oddball.py
@@ -93,7 +93,7 @@ class RecursionTest(CoverageTest):
                 )
 
     def test_long_recursion_recovery(self):
-        # Test the core of bug 93: http://bitbucket.org/ned/coveragepy/issue/93
+        # Test the core of bug 93: https://bitbucket.org/ned/coveragepy/issue/93
         # When recovering from a stack overflow, the Python trace function is
         # disabled, but the C trace function is not.  So if we're using a
         # Python trace function, we won't trace anything after the stack