linux-kernel - [PATCH 0/1] Let Sphinx store cached bytecode under the output dir

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <cover.1745539360.git.mchehab+huawei@kernel.org>
Date: Fri, 25 Apr 2025 08:08:52 +0800
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
	Jonathan Corbet <corbet@....net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
	linux-kernel@...r.kernel.org,
	Akira Yokosawa <akiyks@...il.com>,
	Andy Shevchenko <andriy.shevchenko@...el.com>
Subject: [PATCH 0/1] Let Sphinx store cached bytecode under the output dir

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