[issue18027] distutils should access stat_result timestamps via .st_*time attributes

2016-06-09 Thread Berker Peksag
Berker Peksag added the comment: This is a duplicate of issue 13420. -- nosy: +berker.peksag resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> newer() function in dep_util.py discard changes in the same second ___ P

[issue18027] distutils should access stat_result timestamps via .st_*time attributes

2014-10-02 Thread Mark Lawrence
Mark Lawrence added the comment: @Eric what is your opinion on this? -- nosy: +BreamoreBoy type: -> enhancement versions: +Python 3.5 ___ Python tracker ___

[issue18027] distutils should access stat_result timestamps via .st_*time attributes

2013-05-20 Thread Jakub Wilk
New submission from Jakub Wilk: Currently distutils accesses stat_result timestamps like this: os.stat(source)[ST_MTIME] But, for compatibility with older Python versions, the above method gives you at most 1-second resolution. It should do it like this instead: os.stat(source).st_mtime