Hello. Kitty's __pycache__ files are being compiled with Python optimizations enabled. This generates for example "/usr/lib64/kitty/__pycache__/__main__.cpython-36.opt-1.pyc". However, the opt-1 files aren't being used by kitty, instead kitty is searching for "/usr/lib64/kitty/__pycache__/__main__.cpython-36.pyc". $ qlist kitty | grep __pycache__.*__main__ /usr/lib64/kitty/__pycache__/__main__.cpython-36.opt-1.pyc $ strace kitty true |& grep __pycache__.*__main__ openat(AT_FDCWD, "/usr/bin/../lib64/kitty/__pycache__/__main__.cpython-36.pyc", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) ---- This may be an indication of a larger problem: $ find /usr/lib64 | grep __pycache__.*opt-1.pyc | wc -l 17214 $ find /usr/lib64 | grep __pycache__.*pyc | grep -v opt-1 | wc -l 34181 Is there a way to verify in an automated way whether Python packages are actually using installed __pycache__ files?
kitty currently generates bytecode for all optimization levels I think this is obsolete
