[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

STINNER Victor added the comment: > Um, doesn't the rejection of PEP 410 mean this should be discontinued? There is an issue in shutil.copystat() on copying the timestamp: in this specific use case, we need nanosecond resolution. Guido proposes (in a private mail thread) to add st_atime_ns, s

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Larry Hastings added the comment: Um, doesn't the rejection of PEP 410 mean this should be discontinued? -- nosy: +larry ___ Python tracker ___ _

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

STINNER Victor added the comment: I created the issue #14180 to prepare a refactoring before changing os.*utime*() functions. -- ___ Python tracker ___

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Roundup Robot added the comment: New changeset 67d9595a833c by Victor Stinner in branch 'default': Issue #13964: signal.sigtimedwait() timeout is now a float instead of a tuple http://hg.python.org/cpython/rev/67d9595a833c -- ___ Python tracker

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

STINNER Victor added the comment: Here is a first step: add _PyTime_ObjectToTimespec() to pytime.h and use it for signal.sigtimedwait(). signal.sigtimedwait(sigwait, (timeout_sec, timeout_nsec)) becomes signal.sigtimedwait(sigwait, timeout). I chose pytime.h instead of timefuncs.h because I

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Arfrever Frehtes Taifersar Arahesis added the comment: Updated version of my suggestion: os.futime(fd, (atime, mtime)) os.utime(path, (atime, mtime), flags=0) os.utimeat(dirfd, path, (atime, mtime), flags=0) atime and mtime could be int, float, decimal.Decimal or None. All other os.*utime*() fu

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

STINNER Victor added the comment: signal.sigtimedwait() API should also be changed from: sigtimedwait(sigset, (timeout_sec, timeout_nsec)) to: sigtimedwait(sigset, timeout) where timeout can be an int, float or decimal.Decimal. The function was introduced in Python 3.3, so its API can be c

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Changes by Ross Lagerwall : -- nosy: +rosslagerwall ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

STINNER Victor added the comment: > New changeset 478fb4869c99 by Victor Stinner in branch 'default': > Issue #13964: Split os.*utime*() subsecond tests into multiple tests... Oops, I also commited my change on extract_time() by mistake. But it is not completly a mistake: it was the goal of my

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Roundup Robot added the comment: New changeset 58bd6a58365d by Victor Stinner in branch 'default': Issue #13964: Skip os.*utime*() tests if os.stat() doesn't support timestamp http://hg.python.org/cpython/rev/58bd6a58365d -- ___ Python tracker

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Roundup Robot added the comment: New changeset 478fb4869c99 by Victor Stinner in branch 'default': Issue #13964: Split os.*utime*() subsecond tests into multiple tests to help http://hg.python.org/cpython/rev/478fb4869c99 -- ___ Python tracker

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Arfrever Frehtes Taifersar Arahesis added the comment: I suggest to support the following functions: futimes(fd, (atime, mtime), flags=0) utimes(path, (atime, mtime), flags=0) utimesat(dirfd, path, (atime, mtime), flags=0) And deprecate other functions already present in 3.2. flags argument of

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Roundup Robot added the comment: New changeset c6e9c4d18b36 by Victor Stinner in branch 'default': Issue #13964: Test also os.futimesat() http://hg.python.org/cpython/rev/c6e9c4d18b36 -- ___ Python tracker ___

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

STINNER Victor added the comment: > Current API: Oh, I forgot: - futimesat(dirfd, path[, (atime, mtime)]) This API looks fine. -- ___ Python tracker ___ __

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Roundup Robot added the comment: New changeset d297f9b10c64 by Victor Stinner in branch 'default': Issue #13964: Write tests for new os.*utime*() functions http://hg.python.org/cpython/rev/d297f9b10c64 -- nosy: +python-dev ___ Python tracker

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue13964] os.utimensat() and os.futimes() should accept Decimal, drop os.futimens()

New submission from STINNER Victor : Python 3.3 has 4 new functions to set the access and modification time of a file (only os.utime() was already present in Python 3.2). New functions taking timestamp with a nanonsecond resolution use a tuple of int because the float type doesn't support nano