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, brett.cannon, brian.curtin, eric.araujo, pitrou, techtonik
Date 2011-01-12.01:44:32
SpamBayes Score 8.3831446e-07
Marked as misclassified No
Message-id <1294796674.55.0.0392033123661.issue7662@psf.upfronthosting.co.za>
In-reply-to
Content
I am going to close this as superseded by #9527.  All these issues, current, #9527, and #1647654 are really about Python's lack of access to the system timezone information and #9527 seem to be the most appropriate solution.

My specific concern about proposed time.utcoffset() is that you normally need UTC offset together with current time, but localtime() call followed by utcoffset() may lead to a race condition.
History
Date User Action Args
2011-01-12 01:44:34belopolskysetrecipients: + belopolsky, brett.cannon, pitrou, techtonik, eric.araujo, brian.curtin
2011-01-12 01:44:34belopolskysetmessageid: <1294796674.55.0.0392033123661.issue7662@psf.upfronthosting.co.za>
2011-01-12 01:44:32belopolskylinkissue7662 messages
2011-01-12 01:44:32belopolskycreate