Fix broken links from linkcheck, exclude localhost from check

9 files changed, 17 insertions, 17 deletions

diff --git a/docs/narr/i18n.rst b/docs/narr/i18n.rst
index e64584322..382b75b4a 100644
--- a/docs/narr/i18n.rst
+++ b/docs/narr/i18n.rst
@@ -682,8 +682,8 @@ The add-on `pyramid_jinja2 <https://github.com/Pylons/pyramid_jinja2>`_
 provides a scaffold with an example of how to use internationalization with
 Jinja2 in Pyramid. See the documentation sections `Internalization (i18n)
 <https://docs.pylonsproject.org/projects/pyramid-jinja2/en/latest/#internalization-i18n>`_
-and `Paster Template I18N
-<https://docs.pylonsproject.org/projects/pyramid-jinja2/en/latest/#paster-template-i18n>`_.
+and `pcreate template i18n
+<https://docs.pylonsproject.org/projects/pyramid-jinja2/en/latest/#pcreate-template-i18n>`_.
 
 
 .. index::
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index df3567726..a09900950 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -52,14 +52,14 @@ Modern
 Tested
 ~~~~~~
 
-Untested code is broken by design. The :app:`Pyramid` community has a strong testing culture and our framework reflects that. Every release of :app:`Pyramid` has 100% statement coverage (as measured by `coverage <http://coverage.readthedocs.io/en/latest/>`_) and 95% decision/condition coverage. (as measured by `instrumental <http://instrumental.readthedocs.io/en/latest/intro.html>`_) It is automatically tested using `Travis <https://travis-ci.org/Pylons/pyramid>`_ and `Jenkins <http://jenkins.pylonsproject.org/job/pyramid/>`_ on supported versions of Python after each commit to its GitHub repository. `Official Pyramid add-ons <https://trypyramid.com/resources-extending-pyramid.html>`_ are held to a similar testing standard.
+Untested code is broken by design. The :app:`Pyramid` community has a strong testing culture and our framework reflects that. Every release of :app:`Pyramid` has 100% statement coverage (as measured by `coverage <https://coverage.readthedocs.io/en/latest/>`_) and 95% decision/condition coverage. (as measured by `instrumental <https://instrumental.readthedocs.io/en/latest/intro.html>`_) It is automatically tested using `Travis <https://travis-ci.org/Pylons/pyramid>`_ and `Jenkins <http://jenkins.pylonsproject.org/job/pyramid/>`_ on supported versions of Python after each commit to its GitHub repository. `Official Pyramid add-ons <https://trypyramid.com/resources-extending-pyramid.html>`_ are held to a similar testing standard.
 
 We still find bugs in :app:`Pyramid`, but we've noticed we find a lot fewer of them while working on projects with a solid testing regime.
 
 Documented
 ~~~~~~~~~~
 
-The :app:`Pyramid` documentation is comprehensive. We strive to keep our narrative documentation both complete and friendly to newcomers. We also maintain the :ref:`Pyramid Community Cookbook <cookbook:pyramid-cookbook>` of  recipes demonstrating common scenarios you might face. Contributions in the form of improvements to our documentation are always appreciated. And we always welcome improvements to our `official tutorials <html_tutorials>`_ as well as new contributions to our `community maintained tutorials <tutorials:pyramid-tutorials>`_.
+The :app:`Pyramid` documentation is comprehensive. We strive to keep our narrative documentation both complete and friendly to newcomers. We also maintain the :ref:`Pyramid Community Cookbook <cookbook:pyramid-cookbook>` of  recipes demonstrating common scenarios you might face. Contributions in the form of improvements to our documentation are always appreciated. And we always welcome improvements to our :ref:`official tutorials <html_tutorials>` as well as new contributions to our :ref:`community maintained tutorials <tutorials:pyramid-tutorials>`.
 
 Supported
 ~~~~~~~~~
diff --git a/docs/narr/logging.rst b/docs/narr/logging.rst
index a7ee0f1f8..b21fe1314 100644
--- a/docs/narr/logging.rst
+++ b/docs/narr/logging.rst
@@ -235,7 +235,7 @@ Request Logging with Paste's TransLogger
 
 The :term:`WSGI` design is modular.  Waitress logs error conditions, debugging
 output, etc., but not web traffic.  For web traffic logging, Paste provides the
-`TransLogger <http://pythonpaste.org/modules/translogger.html>`_
+`TransLogger <https://web.archive.org/web/20160707041338/http://pythonpaste.org:80/modules/translogger.html>`_
 :term:`middleware`.  TransLogger produces logs in the `Apache Combined Log
 Format <http://httpd.apache.org/docs/2.2/logs.html#combined>`_.  But
 TransLogger does not write to files; the Python logging system must be
diff --git a/docs/narr/project.rst b/docs/narr/project.rst
index 5234d89d1..1cd36dbf6 100644
--- a/docs/narr/project.rst
+++ b/docs/narr/project.rst
@@ -741,7 +741,7 @@ testing, as well as distributing your application.
    distribute their reusable code.  You can read more about ``setup.py`` files
    and their usage in the `Python Packaging User Guide
    <https://packaging.python.org/>`_ and `Setuptools documentation
-   <http://pythonhosted.org/setuptools/>`_.
+   <https://setuptools.readthedocs.io/en/latest/>`_.
 
 Our generated ``setup.py`` looks like this:
 
@@ -1122,7 +1122,7 @@ inotify support
 By default ``hupper`` will poll the filesystem for changes to all Python
 code. This can be pretty inefficient in larger projects. To be nicer to your
 hard drive, you should install the
-`watchdog <http://pythonhosted.org/watchdog/>`_ package in development.
+`watchdog <https://pythonhosted.org/watchdog/>`_ package in development.
 ``hupper`` will automatically use ``watchdog`` to more efficiently poll the
 filesystem.
 
diff --git a/docs/narr/scaffolding.rst b/docs/narr/scaffolding.rst
index 82ae0f9ac..b962bc274 100644
--- a/docs/narr/scaffolding.rst
+++ b/docs/narr/scaffolding.rst
@@ -27,7 +27,7 @@ found by the ``pcreate`` command.
 To create a scaffold template, create a Python :term:`distribution` to house
 the scaffold which includes a ``setup.py`` that relies on the ``setuptools``
 package.  See `Packaging and Distributing Projects
-<https://packaging.python.org/tutorials/distributing-packages/>`_ for more information
+<https://packaging.python.org/tutorials/packaging-projects/>`_ for more information
 about how to do this.  For example, we'll pretend the distribution you create
 is named ``CoolExtension``, and it has a package directory within it named
 ``coolextension``.
diff --git a/docs/narr/upgrading.rst b/docs/narr/upgrading.rst
index e0482d5a2..6db61a579 100644
--- a/docs/narr/upgrading.rst
+++ b/docs/narr/upgrading.rst
@@ -128,7 +128,7 @@ you can see DeprecationWarnings printed to the console when the tests run.
 
 The ``-Wd`` argument tells Python to print deprecation warnings to the console.
 See `the Python -W flag documentation
-<https://docs.python.org/2/using/cmdline.html#cmdoption-W>`_ for more
+<https://docs.python.org/2/using/cmdline.html#cmdoption-w>`_ for more
 information.
 
 As your tests run, deprecation warnings will be printed to the console
@@ -218,7 +218,7 @@ as explained in :ref:`testing_under_new_release`.
 See `the PYTHONWARNINGS environment variable documentation
 <https://docs.python.org/2/using/cmdline.html#envvar-PYTHONWARNINGS>`_ or `the
 Python -W flag documentation
-<https://docs.python.org/2/using/cmdline.html#cmdoption-W>`_ for more
+<https://docs.python.org/2/using/cmdline.html#cmdoption-w>`_ for more
 information.
 
 Upgrading to the very latest Pyramid release
diff --git a/docs/narr/vhosting.rst b/docs/narr/vhosting.rst
index e4cee9882..8902e8bae 100644
--- a/docs/narr/vhosting.rst
+++ b/docs/narr/vhosting.rst
@@ -26,7 +26,7 @@ Hosting an Application Under a URL Prefix
 ``http://example.com/``).
 
 If you use a "pure Python" environment, this functionality can be provided by
-`rutter <http://rutter.readthedocs.io/en/latest/>`_, forming a "composite"
+`rutter <https://rutter.readthedocs.io/en/latest/>`_, forming a "composite"
 WSGI application.  Alternatively, you can use :term:`mod_wsgi` to serve your
 application, which handles this virtual hosting translation for you "under the
 hood".
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index e8a07202e..11d9f778a 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -407,7 +407,7 @@ various other clients.  In :app:`Pyramid`, form submission handling logic is
 always part of a :term:`view`.  For a general overview of how to handle form
 submission data using the :term:`WebOb` API, see :ref:`webob_chapter` and
 `"Query and POST variables" within the WebOb documentation
-<http://docs.webob.org/en/latest/reference.html#query-post-variables>`_.
+<https://docs.pylonsproject.org/projects/webob/en/latest/reference.html#query-post-variables>`_.
 :app:`Pyramid` defers to WebOb for its request and response implementations,
 and handling form submission data is a property of the request implementation. 
 Understanding WebOb's request API is the key to understanding how to process
diff --git a/docs/narr/webob.rst b/docs/narr/webob.rst
index 4efe783b0..ae76d3500 100644
--- a/docs/narr/webob.rst
+++ b/docs/narr/webob.rst
@@ -22,7 +22,7 @@ instance of the :class:`pyramid.request.Request` class, which is a subclass of
 
 WebOb is a project separate from :app:`Pyramid` with a separate set of authors
 and a fully separate `set of documentation
-<http://docs.webob.org/en/latest/index.html>`_.  :app:`Pyramid` adds some
+<https://docs.pylonsproject.org/projects/webob/en/latest/index.html>`_.  :app:`Pyramid` adds some
 functionality to the standard WebOb request, which is documented in the
 :ref:`request_module` API documentation.
 
@@ -35,7 +35,7 @@ requests and forming WSGI responses.  WebOb is a nice way to represent "raw"
 WSGI requests and responses.  However, we won't cover that use case in this
 document, as users of :app:`Pyramid` don't typically need to use the
 WSGI-related features of WebOb directly.  The `reference documentation
-<http://docs.webob.org/en/latest/reference.html>`_ shows many examples of
+<https://docs.pylonsproject.org/projects/webob/en/latest/reference.html>`_ shows many examples of
 creating requests and using response objects in this manner, however.
 
 .. index::
@@ -302,7 +302,7 @@ to handle this is to add an extra ``view_config`` for the same route, with
 ``request_method`` set to ``OPTIONS``, and set the desired response header
 before returning. You can find examples of response headers `Access control
 CORS, Preflighted requests
-<https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Preflighted_requests>`_.
+<https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#Preflighted_requests>`_.
 
 .. index::
    single: cleaning up after request
@@ -357,7 +357,7 @@ More detail about the request object API is available as follows.
 
 - :class:`pyramid.request.Request` API documentation
 
-- `WebOb documentation <http://docs.webob.org/en/latest/index.html>`_.  All
+- `WebOb documentation <https://docs.pylonsproject.org/projects/webob/en/latest/index.html>`_.  All
   methods and attributes of a ``webob.Request`` documented within the WebOb
   documentation will work with request objects created by :app:`Pyramid`.
 
@@ -496,4 +496,4 @@ More Details
 More details about the response object API are available in the
 :mod:`pyramid.response` documentation.  More details about exception responses
 are in the :mod:`pyramid.httpexceptions` API documentation.  The `WebOb
-documentation <http://docs.webob.org/en/latest/index.html>`_ is also useful.
+documentation <https://docs.pylonsproject.org/projects/webob/en/latest/index.html>`_ is also useful.