From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] doc: fix documentation build with latest setuptools
Date: Thu, 12 Feb 2026 10:32:57 +0100 [thread overview]
Message-ID: <20260212093257.GA8902@pevik> (raw)
In-Reply-To: <DGCV06VWH5W4.2S96MUIO5X4ZL@suse.com>
> On Thu Feb 12, 2026 at 9:48 AM CET, Petr Vorel wrote:
> > Hi Andrea,
> > > Hi!
> > > > Force setuptools to version 81.0.0, which is the last one where linuxdoc
> > > > still can be installed. Also, from python 3.12 setuptools is not
> > > > available anymore when creating a new virtualenv, so we need to force
> > > > its installation to ensure that documentation will be built.
> > Reviewed-by: Petr Vorel <pvorel@suse.cz>
> > +1, higher setuptools version is probably better as it's still working on the
> > oldest distros (than 68 version I added in my patchset). IMHO it'd be good to
> > add (before merge) a comment to requirements.txt that it's just a temporary
> > workaround (once linuxdoc is released I'd upgrade it and remove the dependency).
> > Kind regards,
> > Petr
> It's not a workaround, we need it because python 3.12 removed it from
> virtualenv. It explained in the git commit message in my patch.
It is a workaround in a sense because new linuxdoc master thanks to my fix [1]
will not need setuptools any more (which I explained in my patch). Normally we
would update, but upstream does not have time to release.
Also, new release will use hatch, we'll need to use pyproject.toml instead of
requirements.txt.
Kind regards,
Petr
[1] https://github.com/return42/linuxdoc/commit/19f5e5cbe8fec100d9135cfb7d3f183fa9dc0642
[2] https://hatch.pypa.io/latest/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-02-12 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 16:06 [LTP] [PATCH] doc: fix documentation build with latest setuptools Andrea Cervesato
2026-02-11 16:16 ` Cyril Hrubis
2026-02-12 8:48 ` Petr Vorel
2026-02-12 9:01 ` Andrea Cervesato via ltp
2026-02-12 9:32 ` Petr Vorel [this message]
2026-02-12 9:50 ` Andrea Cervesato via ltp
2026-02-12 16:07 ` Petr Vorel
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=20260212093257.GA8902@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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