Message180109
| Author |
cmcqueen1975 |
| Recipients |
belopolsky, cmcqueen1975, docs@python, dwsarber, ezio.melotti, lemburg, maksbotan, python-dev, r.david.murray |
| Date |
2013年01月16日.21:43:44 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1358372624.63.0.994213163229.issue12758@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Alexander Belopolsky wrote:
> No. Seconds since the epoch is neither local nor UTC. It is just
> an elapsed number of seconds since an agreed upon time called the
> "epoch".
This statement just seems wrong. And I have just been confused by the current documentation, hence finding this issue. In what timezone is the "epoch"? It makes a difference. It seems with the current behaviour, the "epoch" is _in the local timezone_. So I reckon the documentation is unclear, because the way I read it, I interpretted it to mean UTC. I think it does need to state "in local time".
However, what I'd really prefer is a new function that returns the seconds since the epoch in UTC. |
|