On 25-01-19 18:26, Stefan Agner wrote:
> On 25.01.2019 15:35, Mike Looijmans wrote:
>> Most likely the date/time stamps on the files are such that the "py" files
>> appear to be newer.
>
> Indeed, this seems to be the issue. We are using OSTree, which removes
> mtimes. Ricardo (now on CC) also
Most likely the date/time stamps on the files are such that the "py" files
appear to be newer.
A very simple fix would be to simply delete the ".py" files, they aren't
really needed anyway so you'll save a lot of space in the process.
To do this compile-time, you could add something like this
On 25.01.2019 15:35, Mike Looijmans wrote:
> Most likely the date/time stamps on the files are such that the "py" files
> appear to be newer.
Indeed, this seems to be the issue. We are using OSTree, which removes
mtimes. Ricardo (now on CC) also pointed me to the relevant issue in
OSTree:
Hi,
Recently I noticed that Python3 programs got rather slow. Running the
test application took 12.5 seconds. We are using a read-only file system
and I immediately suspected the bytecode cache. After mounting the
rootfs rw, from the second execution on running the test application
took below 4
