[issue13420] newer() function in dep_util.py discard changes in the same second

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If

[issue13420] newer() function in dep_util.py discard changes in the same second

Change by Jakub Wilk : -- nosy: -jwilk ___ Python tracker ___ ___ Python-bugs-list mailing

[issue13420] newer() function in dep_util.py discard changes in the same second

Jakub Wilk added the comment: I don't remember why I needed it. Sorry! -- ___ Python tracker ___

[issue13420] newer() function in dep_util.py discard changes in the same second

Éric Araujo added the comment: For 3.6 and 3.7, we can avoid the original float resolution issue thanks to stat_result.st_mtime_ns. Not sure if 2.7 should be changed. -- ___ Python tracker

[issue13420] newer() function in dep_util.py discard changes in the same second

Changes by Éric Araujo : -- Removed message: https://bugs.python.org/msg302314 ___ Python tracker ___

[issue13420] newer() function in dep_util.py discard changes in the same second

Éric Araujo added the comment: Oh well. Re-reading #11933 I see that st_mtime is a float and may not have the required precision (53 bits for Python floats vs 64 bit for timestamps), so the proposed change would not fix this issue and reopen that one. --

[issue13420] newer() function in dep_util.py discard changes in the same second

Éric Araujo added the comment: Coming back to this, I think this should be a safe change that fixes the issue without previsible downside. Jacob, you opened a bug duplicate of this one: could you say what was the undesirable behaviour caused by the coarse resolution? (I would change

[issue13420] newer() function in dep_util.py discard changes in the same second

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing

[issue13420] newer() function in dep_util.py discard changes in the same second

Éric Araujo mer...@netwok.org added the comment: It’s a bit hard for me to isolate the distutils problem from the CDBS-specific parts (maybe because I’m tired :). For years, sub-second resolution was not supported by distutils, and things were okay as long as the build* commands did the file

[issue13420] newer() function in dep_util.py discard changes in the same second

David Amian dam...@emergya.com added the comment: 2011/11/18 Éric Araujo rep...@bugs.python.org Éric Araujo mer...@netwok.org added the comment: I've a project, in the setup.py file, I've a function called update_prefix, that updates the 'path_project' variable with prefix arguments

[issue13420] newer() function in dep_util.py discard changes in the same second

Éric Araujo mer...@netwok.org added the comment: Hi David. Thanks for reporting the issue. I have to warn you that there is a high bar for distutils changes; due to the mass of code out there that relies on undocumented internal behavior or works around old bugs, a feature freeze is in

[issue13420] newer() function in dep_util.py discard changes in the same second

David Amian dam...@emergya.com added the comment: sorry, I didn't explain well. I've a project, in the setup.py file, I've a function called update_prefix, that updates the 'path_project' variable with prefix arguments from setup.py If you runs setup.py with --prefix=/usr, then the file in

[issue13420] newer() function in dep_util.py discard changes in the same second

Éric Araujo mer...@netwok.org added the comment: I've a project, in the setup.py file, I've a function called update_prefix, that updates the 'path_project' variable with prefix arguments from setup.py If you runs setup.py with --prefix=/usr, then the file in

[issue13420] newer() function in dep_util.py discard changes in the same second

New submission from David Amian dam...@emergya.com: Hi, I had a problem making deb packages with distutils and cdbs. Looking for any solution, I found Issue 11933 and saw that the newer() method has been changed, using [ST_MTIME] instead of st_mtime. This commit is to solve Issue 10148 that