Hi, I'm packaging a couple of python3 modules for Leaps with a current Python 3.8, and noticed, that Leap builds tend to warn about: python3-pysnmp-apps.noarch: W: python-bytecode-inconsistent-mtime /usr/lib/python3.8/site-packages/pysnmp_apps/__pycache__/__init__.cpython-38.opt-1.pyc 1970-01-01T00:00:03 /usr/lib/python3.8/site-packages/pysnmp_apps/__init__.py 2018-01-07T08:15:27 eg. here: https://build.opensuse.org/package/live_build_log/home:frispete:python/pytho... My gut feeling is, that the zeroed timestamp is enforced by Python 3.8, and hence a false warning. Or do I have to expect: [ 4s] The timestamp embedded in this python bytecode file isn't equal to the mtime [ 4s] of the original source file, which will force the interpreter to recompile the [ 4s] .py source every time, ignoring the saved bytecode. Cheers, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org