qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v2 0/1] readthedoc theme patch
Date: Thu, 13 May 2021 18:17:39 +0100	[thread overview]
Message-ID: <CAFEAcA_BTwg2KyyfsG8Q2_FFzKuYN+5J0X85OBpN-x=-5PFANw@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1C+V=x8=tcm0WhtFxS5P_4WjLNVXOVKEnvgWpmFDwom6-Q@mail.gmail.com>

On Thu, 13 May 2021 at 17:03, Marc-André Lureau
<marcandre.lureau@gmail.com> wrote:
> This should work, can you check?:
>
> diff --git a/docs/conf.py b/docs/conf.py
> index 3802b70d62..9e3d7cee0e 100644
> --- a/docs/conf.py
> +++ b/docs/conf.py
> @@ -29,6 +29,7 @@
>  import os
>  import sys
>  import sphinx
> +from packaging.version import parse as parse_version
>  from sphinx.errors import ConfigError
>
>  # Make Sphinx fail cleanly if using an old Python, rather than obscurely
> @@ -162,7 +163,7 @@
>  # Theme options are theme-specific and customize the look and feel of a theme
>  # further.  For a list of options available for each theme, see the
>  # documentation.
> -if html_theme == 'sphinx_rtd_theme':
> +if parse_version(sphinx_rtd_theme.__version__) >= parse_version('0.4.3'):
>      html_theme_options = {
>          "style_nav_header_background": "#802400",
>      }

This fails:

../../docs/meson.build:30: WARNING: /usr/bin/sphinx-build:
Configuration error:
There is a programable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/config.py", line 157, in __init__
    execfile_(filename, config)
  File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line
150, in execfile_
    exec_(code, _globals)
  File "conf.py", line 32, in <module>
    from packaging.version import parse as parse_version
ModuleNotFoundError: No module named 'packaging'




> However, we agreed before to not have support fallbacks for missing deps. Perhaps we should require rtd >= 0.4.3 instead?

That would prevent the docs from building on too many platforms,
I think. 0.4.3 was only released upstream in Feb 2019.

thanks
-- PMM


  reply	other threads:[~2021-05-13 17:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 13:06 [PULL v2 0/1] readthedoc theme patch marcandre.lureau
2021-05-10 13:06 ` [PULL v2 1/1] sphinx: adopt kernel readthedoc theme marcandre.lureau
2021-05-12 13:43 ` [PULL v2 0/1] readthedoc theme patch Peter Maydell
2021-05-12 15:17   ` Marc-André Lureau
2021-05-12 15:54     ` Peter Maydell
2021-05-12 16:02       ` Marc-André Lureau
2021-05-12 16:17         ` Peter Maydell
2021-05-12 19:31           ` Peter Maydell
2021-05-13 13:45             ` Peter Maydell
2021-05-13 16:03               ` Marc-André Lureau
2021-05-13 17:17                 ` Peter Maydell [this message]
2021-05-14  8:00                   ` Marc-André Lureau
2021-05-14  9:10                     ` Peter Maydell

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='CAFEAcA_BTwg2KyyfsG8Q2_FFzKuYN+5J0X85OBpN-x=-5PFANw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).