All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [OT] trying to build kas docs, "No module named 'sphinxarg'"
Date: Thu, 26 Jun 2025 10:38:20 +0200	[thread overview]
Message-ID: <DAWBUTM7CWGG.3S2D24JNNJ89G@bootlin.com> (raw)
In-Reply-To: <edad802f-c9fb-a11a-e729-bc505ac97112@crashcourse.ca>

On Wed Jun 25, 2025 at 8:34 PM CEST, Robert P. J. Day wrote:
>
> Given the abudance of Sphinx expertise here, I'm hoping people will
> forgive me for a little off-topic querying ... I checked out kas:
>
>   https://github.com/siemens/kas.git
>
> and tried to build the Sphinx docs with:
>
>   $ make html
>
> and got:
>
> Generate kas-container usage documentation
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v7.4.7
> loading translations [en]... done
>
> Extension error:
> Could not import extension sphinxarg.ext (exception: No module named
> 'sphinxarg')
> make: *** [Makefile:53: html] Error 2
>
>
> I've installed python3-configargparse, but no change. Can anyone
> suggest what I need to fetch and install? Thank you kindly.

You probably just need to install sphinx-argparse.
https://sphinx-argparse.readthedocs.io/en/latest/

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-06-26  8:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 18:34 [OT] trying to build kas docs, "No module named 'sphinxarg'" Robert P. J. Day
2025-06-26  8:38 ` Antonin Godard [this message]
2025-06-26  9:14   ` [docs] " Robert P. J. Day
2025-06-26  9:35     ` Gyorgy Sarvari

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=DAWBUTM7CWGG.3S2D24JNNJ89G@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=rpjday@crashcourse.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.