➜

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.

作者 belopolsky
收信人 Alexander.Belopolsky, Alexandre.Zani, barry, belopolsky, djc, lemburg, r.david.murray
日期 2012-06-05.01:28:11
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <1338859693.45.0.169663010472.issue14908@psf.upfronthosting.co.za>
In-reply-to
内容
Barry,

I looked at your changeset at http://bazaar.launchpad.net/~gwibber-committers/gwibber/trunk/revision/1354 and at the specification at http://developers.facebook.com/docs/reference/api/event/.

Am I correct that you are parsing "string containing an ISO-8601 formatted date/time or a UNIX timestamp; if it contains a time zone (not recommended), it will be converted to Pacific time before being stored and displayed"?

If so, it looks like converting input to POSIX timestamps is the wrong thing to do because users who specify naive time expect it to be displayed without conversion.

The way I read the specs, a better implementation would store input in naive datetime objects, converting UNIX timestamps or TZ-aware strings to Pacific timezone.
历史
日期 用户 动作 参数
2012-06-05 01:28:13belopolsky修改recipients: + belopolsky, lemburg, barry, djc, r.david.murray, Alexander.Belopolsky, Alexandre.Zani
2012-06-05 01:28:13belopolsky修改messageid: <1338859693.45.0.169663010472.issue14908@psf.upfronthosting.co.za>
2012-06-05 01:28:12belopolsky链接issue14908 messages
2012-06-05 01:28:11belopolsky创建