So, I got some help from StackOverflow on this one.
Careful use of the dateutil library seemed to solve my problem. It is
fairly robust and a much smaller footprint from PyTZ.
On Mar 10, 11:06 am, mawcs mwilliam...@williamsonclan.us wrote:
(I am new to Python and Google App Engine, please
Not so hurry.
As for pytz footprint, it's ~600kB in size and can be lightning fast
if combined with caching in memcache (caching of tzinfo? why not...).
Combine this with Babel and you'll get everything you'd want to do
l10n.
On 10 Mar, 20:21, mawcs mwilliam...@williamsonclan.us wrote:
So, I
On Mar 11, 6:06 am, mawcs mwilliam...@williamsonclan.us wrote:
I'm having a helluva time trying to manage multiple user timezones in
my Google App Engine application.
I have wrangled with time display for years, and my solution is to
store everything as a unix datestamp (time.time()). When the
