Message 231606 - Python tracker

➜

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	barry, belopolsky, errx, mitya57, r.david.murray
Date	2014-11-24.16:08:14
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1416845294.22.0.671624967248.issue22752@psf.upfronthosting.co.za>
In-reply-to

Content
> Is it possible to set timezone based on localtime(current_time) where current_time is the result of time() call? No. time.timezone is a constant it cannot change with time. This is a limitation of the POSIX and C standards on which time module is based. > For example, my mail sending program uses `email.utils.formatdate(localtime=True)', and that is returning a time one hour in the past currently. I thought email.utils.formatdate was fixed in 3.x series. Can you report this as a separate issue?

> Is it possible to set timezone based on localtime(current_time) where current_time is the result of time() call?

No. time.timezone is a constant it cannot change with time.  This is a limitation of the POSIX and C standards on which time module is based.

> For example, my mail sending program uses `email.utils.formatdate(localtime=True)', and that is returning a time one hour in the past currently.

I thought email.utils.formatdate was fixed in 3.x series.  Can you report this as a separate issue?

History
Date	User	Action	Args
2014-11-24 16:08:14	belopolsky	set	recipients: + belopolsky, barry, r.david.murray, errx, mitya57
2014-11-24 16:08:14	belopolsky	set	messageid: <1416845294.22.0.671624967248.issue22752@psf.upfronthosting.co.za>
2014-11-24 16:08:14	belopolsky	link	issue22752 messages
2014-11-24 16:08:14	belopolsky	create