Message 180150 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	neologix
Recipients	bkabrda, neologix, richmose
Date	2013-01-17.19:53:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1358452434.52.0.542953502509.issue15448@psf.upfronthosting.co.za>
In-reply-to

Content
There are actually two distinct issues. For the first one, the problem is really a distribution issue: the libc is more recent than the kernel, and exports *utimes() whereas the kernel doesn't implement those syscalls, which results in ENOSYS. I don't like the idea of adding explicit check for this, because any syscall can fail with ENOSYS (we've had recently pipe2(), accept4(), etc). It's really a distribution issue. For the second one, it seems that RHEL6.4 doesn't have utime() anymore, which I find really strange (although POSIX.1-2008 marks utime() as obsolete). Could you provide the output of: $ strace ./python -c "import os; os.utime('.')"

There are actually two distinct issues.

For the first one, the problem is really a distribution issue: the libc is more recent than the kernel, and exports *utimes() whereas the kernel doesn't implement those syscalls, which results in ENOSYS.
I don't like the idea of adding explicit check for this, because any syscall can fail with ENOSYS (we've had recently pipe2(), accept4(), etc).
It's really a distribution issue.

For the second one, it seems that RHEL6.4 doesn't have utime() anymore, which I find really strange (although POSIX.1-2008 marks utime() as obsolete).
Could you provide the output of:
$ strace ./python -c "import os; os.utime('.')"

History
Date	User	Action	Args
2013-01-17 19:53:54	neologix	set	recipients: + neologix, bkabrda, richmose
2013-01-17 19:53:54	neologix	set	messageid: <1358452434.52.0.542953502509.issue15448@psf.upfronthosting.co.za>
2013-01-17 19:53:54	neologix	link	issue15448 messages
2013-01-17 19:53:53	neologix	create