homepage

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 belopolsky
Recipients belopolsky, docs@python, ezio.melotti, lemburg, maksbotan
Date 2011年08月17日.00:42:01
SpamBayes Score 6.0972627e-05
Marked as misclassified No
Message-id <1313541722.75.0.00986554464106.issue12758@psf.upfronthosting.co.za>
In-reply-to
Content
> Return the local time as a floating point number
> expressed in seconds since the epoch.
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". 
I would say: "Return the current time as a floating point number representing the number of seconds elapsed since the epoch." Suggestions for a shorter formulation that would not change the meaning are welcome. Maybe "Return the number of seconds elapsed since the epoch as a floating point number."
History
Date User Action Args
2011年08月17日 00:42:03belopolskysetrecipients: + belopolsky, lemburg, ezio.melotti, docs@python, maksbotan
2011年08月17日 00:42:02belopolskysetmessageid: <1313541722.75.0.00986554464106.issue12758@psf.upfronthosting.co.za>
2011年08月17日 00:42:02belopolskylinkissue12758 messages
2011年08月17日 00:42:01belopolskycreate

AltStyle によって変換されたページ (->オリジナル) /