- remove intersphinx usage, the overhead of re-fetching

inventory on every build not worth it

Change-Id: I3c4506b246d0f327c4b56afa723975daee984476

doc/build/conf.py

@@ -34,11 +34,9 @@ import sqlalchemy
 
 extensions = [
             'sphinx.ext.autodoc',
-            'sphinx.ext.intersphinx',
-                'zzzeeksphinx',
-                'changelog',
-                'sphinx_paramlinks',
-                #'corrections'
+            'zzzeeksphinx',
+            'changelog',
+            'sphinx_paramlinks',
             ]
 
 # Add any paths that contain templates here, relative to this directory.
@@ -341,9 +339,4 @@ epub_copyright = u'2007-2015, SQLAlchemy authors'
 # Allow duplicate toc entries.
 #epub_tocdup = True
 
-intersphinx_mapping = {
-    'alembic': ('http://alembic.zzzcomputing.com/en/latest/', None),
-    'psycopg2': ('http://pythonhosted.org/psycopg2', None),
-}
-
 

doc/build/core/constraints.rst

@@ -561,7 +561,7 @@ name as follows::
     :paramref:`.MetaData.naming_convention` - for additional usage details
     as well as a listing of all available naming components.
 
-    :ref:`alembic:tutorial_constraint_names` - in the Alembic documentation.
+    `The Importance of Naming Constraints <http://alembic.zzzcomputing.com/en/latest/naming.html>`_ - in the Alembic documentation.
 
 .. versionadded:: 0.9.2 Added the :paramref:`.MetaData.naming_convention` argument.
 

doc/build/dialects/postgresql.rst

@@ -131,12 +131,12 @@ mixin:
 
 When instantiating models that use these column types, you should pass
 whatever data type is expected by the DBAPI driver you're using for
-the column type. For :mod:`psycopg2` these are
-:class:`~psycopg2.extras.NumericRange`,
-:class:`~psycopg2.extras.DateRange`,
-:class:`~psycopg2.extras.DateTimeRange` and
-:class:`~psycopg2.extras.DateTimeTZRange` or the class you've
-registered with :func:`~psycopg2.extras.register_range`.
+the column type. For ``psycopg2`` these are
+``psycopg2.extras.NumericRange``,
+``psycopg2.extras.DateRange``,
+``psycopg2.extras.DateTimeRange`` and
+``psycopg2.extras.DateTimeTZRange`` or the class you've
+registered with ``psycopg2.extras.register_range``.
 
 For example: