linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: [PATCH 0/1] Let Sphinx store cached bytecode under the output dir
Date: Fri, 25 Apr 2025 08:08:52 +0800	[thread overview]
Message-ID: <cover.1745539360.git.mchehab+huawei@kernel.org> (raw)

Hi Jon,

I guess we can also apply this one. It works fine for documentation, as
it will store the __pycache__ directory under Documentation/output,
and should properly honor O=, as this is already handled by the doc
output logic. Also, make cleandocs will remove the entire output dir,
including the bytecode files and dir.

So, this should work fine for us.

IMO, we still need a generic solution to cover the other cases where
we're using PYTHONDONTWRITEBYTECODE=1, but, as on Sphinx
there are 634 temp files, this could hopefully speedup doc builds
a little bit on slower machines and/or when one is just rebuilding
docs with small changes.

Mauro Carvalho Chehab (1):
  docs: Makefile: store __pycache__ at the output directory

 Documentation/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.49.0



             reply	other threads:[~2025-04-25  0:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25  0:08 Mauro Carvalho Chehab [this message]
2025-04-25  0:08 ` [PATCH 1/1] docs: Makefile: store __pycache__ at the output directory Mauro Carvalho Chehab
2025-04-25 18:10   ` Andy Shevchenko
2025-04-28 23:57     ` Jonathan Corbet
2025-04-30 15:42       ` Mauro Carvalho Chehab

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=cover.1745539360.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).