[issue5720] ctime: I don't think that word means what you think it means.

Zooko Wilcox-O'Hearn added the comment: Aha! Mystery solved. I wouldn't say that you were stupid — I would say that "crtime" is way too close to "ctime", and I strongly agree with the suggestion (http://mail.python.org/pipermail/python-dev/2009-June/090026.html) on the mailing list by Greg Ewi

[issue5720] ctime: I don't think that word means what you think it means.

Benjamin Peterson added the comment: You're quite right. I stupidly misread "crtime" as "ctime". -- ___ Python tracker ___ ___ Python-b

[issue5720] ctime: I don't think that word means what you think it means.

Zooko Wilcox-O'Hearn added the comment: Benjamin: I'm sorry, I still don't understand. Do you think my proposal would involve setting something named "ctime" to contain a value that didn't come from the underlying stat "ctime"? -- ___ Python tracker

[issue5720] ctime: I don't think that word means what you think it means.

Benjamin Peterson added the comment: Indeed, "hijacking" is a bit strong. I mean filling it with a value that is not in the underlying st_ctime field from stat() call. -- ___ Python tracker

[issue5720] ctime: I don't think that word means what you think it means.

Zooko Wilcox-O'Hearn added the comment: Benjamin Peterson: what do you mean "hijack ctime"? I don't think I — or anyone — has proposed anything that fits that description. Please be more specific. My proposal in http://bugs.python.org/issue5720#msg85750 does not break anything. -- _

[issue5720] ctime: I don't think that word means what you think it means.

Benjamin Peterson added the comment: I don't think we should hijack st_ctime. All the other members of the stat object correspond exactly to what you get back from the Unix stat() call. Let's not break that. How about just leaving st_ctime as it is and adding st_creationtime, which will have t

[issue5720] ctime: I don't think that word means what you think it means.

Zooko Wilcox-O'Hearn added the comment: Well, read the thread! http://mail.python.org/pipermail/python-dev/2009-June/090021.html Basically just a couple of +1's, and a good suggestion to name it something clearer than "crtime". Please fix it! -- nosy: +Zooko.Wilcox-O'Hearn ___

[issue5720] ctime: I don't think that word means what you think it means.

Ezio Melotti added the comment: What was the outcome? -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue5720] ctime: I don't think that word means what you think it means.

Changes by Ramchandra Apte : -- versions: +Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue5720] ctime: I don't think that word means what you think it means.

Zooko O'Whielacronx added the comment: Okay, I posted to python-dev: http://mail.python.org/pipermail/python-dev/2009-June/090021.html -- ___ Python tracker ___

[issue5720] ctime: I don't think that word means what you think it means.

Antoine Pitrou added the comment: Sounds like a good idea, perhaps you could launch a discussion on python-dev? -- nosy: +pitrou ___ Python tracker ___ __

[issue5720] ctime: I don't think that word means what you think it means.

New submission from Zooko O'Whielacronx : The stat module currently uses the "st_ctime" slot to hold two kinds values which are semantically different but which are frequently confused with one another. It chooses which kind of value to put in there based on platform -- Windows gets the file cre