public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mitch Deoudes <mitch@houseofpain.org>
To: cygwin@cygwin.com
Subject: Re: Re: cygwin python os.stat gives wrong ctime
Date: Mon, 30 May 2016 08:09:00 -0000	[thread overview]
Message-ID: <574B42EA.9060408@houseofpain.org> (raw)
In-Reply-To: <4026b0f6-0514-576e-def4-c5fcd79148b9@cs.umass.edu>



On 5/28/2016 10:35 PM, Eliot Moss wrote:
> On 5/28/2016 9:39 PM, Mitch Deoudes wrote:
>> According to the python docs, os.stat() gives the following for 
>> st_ctime:
>>
>>     "|st_ctime| - platform dependent; time of most recent metadata 
>> change on Unix, or the time of
>> creation on Windows"
>
> cygwin emulates posix, so you should expect a posix-like result.

I understand your argument, and offer the following, which is from the 
same section of the python docs:

     "On other Unix systems (such as FreeBSD), the following attributes 
may be available (but may be only filled out if root tries to use them):

  * |st_birthtime| - time of file creation"

Suggesting that it's not "anti-POSIX" (unPOSIX?  aPOSIX?) to provide the 
information if it's available.

Anyway, I've found a more or less suitable workaround for now, batching 
up the queries and calling out to the shell - so I'll leave it at that.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-05-29 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 10:14 Mitch Deoudes
2016-05-29 10:58 ` Eliot Moss
2016-05-30  8:09   ` Mitch Deoudes [this message]
2016-05-30 17:00     ` Eliot Moss
2016-05-30  9:38 ` Corinna Vinschen
2016-05-31  9:17   ` Yaakov Selkowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=574B42EA.9060408@houseofpain.org \
    --to=mitch@houseofpain.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).