Message133072
| Author |
belopolsky |
| Recipients |
Jay.Taylor, Neil Muller, amaury.forgeotdarc, andersjm, belopolsky, catlee, davidfraser, erik.stephens, guettli, hodgestar, jribbens, lemburg, mark.dickinson, ping, pitrou, r.david.murray, steve.roberts, tim.peters, tomster, vivanov, vstinner, werneck |
| Date |
2011年04月05日.18:32:31 |
| SpamBayes Score |
2.233369e-11 |
| Marked as misclassified |
No |
| Message-id |
<BANLkTik2QYcwLSNF-zHJn_-_o1VeCdoD6Q@mail.gmail.com> |
| In-reply-to |
<4D9B5516.8090606@egenix.com> |
| Content |
On Tue, Apr 5, 2011 at 1:45 PM, Marc-Andre Lemburg
<report@bugs.python.org> wrote:
..
> BTW: A "timestamp" usually refers to the combination of date and
> time. The time.time() return value is "seconds since the Epoch".
> I usually call those values "ticks" (not sure whether it's standard
> term of not, but always writing "seconds since Epoch" wasn't an
> option either ;-)).
In Unix context, the term "timestamp" is usually associated with the
various time values that OS stores with the files. I think this use
is due to the analogy with physical "received on" timestamps used on
paper documents. Since it is well-known that Unix filesystems store
time values as seconds since Epoch, it is common to refer to these
values as "Unix timestamps".
See, for example:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/touch.html |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年04月05日 18:32:33 | belopolsky | set | recipients:
+ belopolsky, lemburg, tim.peters, ping, jribbens, guettli, amaury.forgeotdarc, mark.dickinson, davidfraser, pitrou, andersjm, catlee, vstinner, tomster, werneck, hodgestar, Neil Muller, erik.stephens, steve.roberts, r.david.murray, vivanov, Jay.Taylor |
| 2011年04月05日 18:32:32 | belopolsky | link | issue2736 messages |
| 2011年04月05日 18:32:31 | belopolsky | create |
|