[issue3425] posixmodule.c always using res = utime(path, NULL)

R. David Murray added the comment: This is no longer an issue in Python3; there utimes is used if it is available (if utimensat is not). Since this doesn't affect the platforms actually supported by python2.7, I'm closing this as out of date. -- nosy: +r.david.murray resolution: -> o

[issue3425] posixmodule.c always using res = utime(path, NULL)

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5 ___ Python tracker ___ ___ Python-bugs-list ma

[issue3425] posixmodule.c always using res = utime(path, NULL)

John Szakmeister added the comment: It seems reasonable to prefer utimes() over utime() in all cases, when utimes() is available, since utime() is considered obsolete. I've attached a patch with the required change and ran all the tests. There are some tests failing on trunk with my system.

[issue3425] posixmodule.c always using res = utime(path, NULL)

New submission from Oskar Andersson <[EMAIL PROTECTED]>: I'm porting, embedding and extending Python in a very limited environment. This environment does not have utime.h and have not defined the following function: int utime(const char *, const struct utimbuf *); Although the function called