© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
It matters because if we're building on NTFS we can have a py file with an odd timestamp, which is correctly put in the pyo file as an odd integer. On unpacking to a FAT drive the py file mtime is evened due to the 2 second resolution, and no longer matches the pyo timestamp.
The linked branch now also disables the Inno rounding, and optionally lp:~gz/bzr/installer_plugin_script_timestamp_rounding covers the corner case of installing onto FAT.