Martin v. Löwis <mar...@v.loewis.de> added the comment: > I don't want to remove os.futimens() and os.utimensat() because they add a > feature: UTIME_NOW and UTIME_OMIT flags.
I'm not sure how this could work: UTIME_NOW and UTIME_OMIT have typically values such as ((1l << 30) - 2l) which could be mistaken as a time stamp if there is a flat nanosecond value. There would be ways to solve this, of course: not passing the value should be considered as UTIME_OMIT, and passing -1 may be treated as UTIME_NOW. ---------- title: add st_*time_ns fileds to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds -> add st_*time_ns fileds to os.stat(), add ns keyword to os.*utime*(), os.*utimens*() expects a number of nanoseconds _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14127> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
