While the building system doesn't create any Python JIT bytecode,
if one manually runs kernel-doc.py or get_abi.py, Python will,
by default, create a bytecode and store it under scripts/lib/*.

This is normal, and not controlled by the Kernel itself. So,
add *.pyc as an extension to be ignored.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index f2f63e47fb88..2e01bc0b2d2a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -39,6 +39,7 @@
 *.mod.c
 *.o
 *.o.*
+*.pyc
 *.patch
 *.rmeta
 *.rpm
-- 
2.49.0

On Wed, Apr 16, 2025 at 02:57:39PM +0800, Mauro Carvalho Chehab wrote:
> While the building system doesn't create any Python JIT bytecode,
> if one manually runs kernel-doc.py or get_abi.py, Python will,
> by default, create a bytecode and store it under scripts/lib/*.
> 
> This is normal, and not controlled by the Kernel itself. So,
> add *.pyc as an extension to be ignored.

...

>  *.mod.c
>  *.o
>  *.o.*
> +*.pyc

Shouldn't we prevent the order? (This should go after the "patch")

>  *.patch
>  *.rmeta
>  *.rpm

...

P.S. I'm going to test the first patch (at least) soon.

-- 
With Best Regards,
Andy Shevchenko