DPDK patches and discussions
 help / color / mirror / Atom feed
From: Paul Szczepanek <paul.szczepanek@arm.com>
To: dev@dpdk.org
Cc: probb@iol.unh.edu, Paul Szczepanek <paul.szczepanek@arm.com>,
	Luca Vizzarro <luca.vizzarro@arm.com>
Subject: [PATCH] dts: remove external dependency on python docs
Date: Fri,  8 Nov 2024 16:29:45 +0000	[thread overview]
Message-ID: <20241108162945.699545-1-paul.szczepanek@arm.com> (raw)

Sphinx can link to online python docs but doing so
creates a requirement for an internet connection.
This commit removes this dependency.

Signed-off-by: Paul Szczepanek <paul.szczepanek@arm.com>
Reviewed-by: Luca Vizzarro <luca.vizzarro@arm.com>
---
 doc/guides/conf.py | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/guides/conf.py b/doc/guides/conf.py
index b553d9d5bf..b1ad3bb5a6 100644
--- a/doc/guides/conf.py
+++ b/doc/guides/conf.py
@@ -59,7 +59,7 @@
 
 # DTS API docs additional configuration
 if environ.get('DTS_DOC_BUILD'):
-    extensions = ['sphinx.ext.napoleon', 'sphinx.ext.autodoc', 'sphinx.ext.intersphinx']
+    extensions = ['sphinx.ext.napoleon', 'sphinx.ext.autodoc']
     # Napoleon enables the Google format of Python doscstrings.
     napoleon_numpy_docstring = False
     napoleon_attr_annotations = True
@@ -76,9 +76,6 @@
     autodoc_typehints_format = 'short'
     autodoc_typehints_description_target = 'documented'
 
-    # Intersphinx allows linking to external projects, such as Python docs.
-    intersphinx_mapping = {'python': ('https://docs.python.org/3', None)}
-
     # DTS docstring options.
     add_module_names = False
     toc_object_entries = True
-- 
2.39.2


             reply	other threads:[~2024-11-08 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 16:29 Paul Szczepanek [this message]
2024-11-08 16:43 ` Patrick Robb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241108162945.699545-1-paul.szczepanek@arm.com \
    --to=paul.szczepanek@arm.com \
    --cc=dev@dpdk.org \
    --cc=luca.vizzarro@arm.com \
    --cc=probb@iol.unh.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).