linux-kernel - Re: [PATCH v3 0/2] Don't create Python bytecode when building the kernel

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5cc4d9dd-496e-4512-a683-272b1b84d98b@gmail.com>
Date: Wed, 23 Apr 2025 18:30:48 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: andriy.shevchenko@...el.com
Cc: airlied@...il.com, corbet@....net, dmitry.baryshkov@....qualcomm.com,
 dri-devel@...ts.freedesktop.org, intel-gfx@...ts.freedesktop.org,
 jani.nikula@...ux.intel.com, joonas.lahtinen@...ux.intel.com,
 linux-doc@...r.kernel.org, linux-kbuild@...r.kernel.org,
 linux-kernel@...r.kernel.org, maarten.lankhorst@...ux.intel.com,
 masahiroy@...nel.org, mchehab+huawei@...nel.org, mripard@...nel.org,
 nathan@...nel.org, nicolas.schier@...ux.dev, rodrigo.vivi@...el.com,
 simona@...ll.ch, tursulin@...ulin.net, tzimmermann@...e.de
Subject: Re: [PATCH v3 0/2] Don't create Python bytecode when building the
 kernel

Hi Andy,

On Tue, 22 Apr 2025 10:57:33 +0300, Andy Shevchenko wrote:
> On Mon, Apr 21, 2025 at 10:35:29AM -0600, Jonathan Corbet wrote:
>> Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com> writes:
[...]

>> > Would it be possible to properly support O= and create pyc / pycache
>> > inside the object/output dir?
>> 
>> I have to confess, I've been wondering if we should be treating the .pyc
>> files like we treat .o files or other intermediate products.  Rather
>> than trying to avoid their creation entirely, perhaps we should just be
>> sure they end up in the right place and are properly cleaned up...?
>> 
>> To answer Dmitry's question, it seems that setting PYTHONPYCACHEPREFIX
>> should do the trick?
> 
> It's not so easy. The Python is written in a way that it thinks it will never
> runs object files separately from the source. Hence that variable sets only
> the folder per script as _home_ for the cache. It's completely unusable. They
> took it wrong. It still can be _painfully_ used, but it will make Makefiles
> uglier.

But, PYTHONPYCACHEPREFIX can be set as an environment variable.

For example, try:

    export PYTHONPYCACHEPREFIX="$HOME/.cache/__pycache__"

Wouldn't it be good enough for you?

Regards,
Akira