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 jsjgruber
Recipients eric.araujo, jsjgruber, tarek
Date 2011-04-27.17:36:05
SpamBayes Score 2.6144054e-09
Marked as misclassified No
Message-id <1303925770.06.0.8293729599.issue11933@psf.upfronthosting.co.za>
In-reply-to
Content
I can understand what you are saying about side effects.

I was trying to suggest that the move to stat.st_mtime in dep_util.py in the hg commit I mentioned be reverted back to use stat[ST_MTIME], thereby matching the other python releases and the old behavior (and matching file_util.py). It seems to me that would be the safest course when it comes to side-effects.

If it were desired to determine which file was newer using sub-second values, perhaps that would make a reasonable change in distutils2, but files created with a few microseconds would have to be considered equivalent due to the reduced precision available in python floats (53 bits on my platform, if I understand correctly) as compared to the 64 bit precision used by some operating systems and file systems.

However, I think I'd prefer to turn the decision and further process over to you, if you don't mind. I thank you and your colleagues for your excellent work with python, and with making it platform independent--a very difficult part of the work indeed.
History
Date User Action Args
2011-04-27 17:36:10jsjgrubersetrecipients: + jsjgruber, tarek, eric.araujo
2011-04-27 17:36:10jsjgrubersetmessageid: <1303925770.06.0.8293729599.issue11933@psf.upfronthosting.co.za>
2011-04-27 17:36:06jsjgruberlinkissue11933 messages
2011-04-27 17:36:05jsjgrubercreate