Message 149984 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	barry, brett.cannon, ncoghlan, neologix, pitrou
Date	2011-12-21.12:54:11
SpamBayes Score	0.0003763031
Marked as misclassified	No
Message-id	<1324472052.82.0.52069101893.issue13645@psf.upfronthosting.co.za>
In-reply-to

Content
The pyc format currently stores the modification time cast to a 32-bit int. A 3.3 iteration of the pyc format could instead store two 32-bit ints, one for the integral part and one for the fractional part (e.g. in nanoseconds). When HAVE_STAT_TV_NSEC is defined, struct stat has a "st_mtim" member which is a struct timespec providing theoretical nanosecond precision. Whether this would be useful remains to be decided.

The pyc format currently stores the modification time cast to a 32-bit int. A 3.3 iteration of the pyc format could instead store two 32-bit ints, one for the integral part and one for the fractional part (e.g. in nanoseconds). When HAVE_STAT_TV_NSEC is defined, struct stat has a "st_mtim" member which is a struct timespec providing theoretical nanosecond precision.

Whether this would be useful remains to be decided.

History
Date	User	Action	Args
2011-12-21 12:54:13	pitrou	set	recipients: + pitrou, barry, brett.cannon, ncoghlan, neologix
2011-12-21 12:54:12	pitrou	set	messageid: <1324472052.82.0.52069101893.issue13645@psf.upfronthosting.co.za>
2011-12-21 12:54:12	pitrou	link	issue13645 messages
2011-12-21 12:54:12	pitrou	create