Message 186776 - 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	sijinjoseph
Recipients	belopolsky, brian.curtin, cm, lemburg, r.david.murray, sijinjoseph, terry.reedy, tim.golden
Date	2013-04-13.18:11:24
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1365876684.58.0.690479870915.issue17627@psf.upfronthosting.co.za>
In-reply-to

Content
This is the same as issue10634 Problem is with the Windows CRT implementation of localtime which does not seem to be using updated timezone information. Can this become an issue with technologies like vMotion which allow Live Migration of virtual servers across data centers in different timezones? One way to address maybe to somehow reset the CRT timezone structures on Windows prior to a call to localtime. Does this seem like a good approach? Is the issue worth pursuing?

This is the same as issue10634

Problem is with the Windows CRT implementation of localtime which does not seem to be using updated timezone information.

Can this become an issue with technologies like vMotion which allow Live Migration of virtual servers across data centers in different timezones?

One way to address maybe to somehow reset the CRT timezone structures on Windows prior to a call to localtime. Does this seem like a good approach? Is the issue worth pursuing?

History
Date	User	Action	Args
2013-04-13 18:11:24	sijinjoseph	set	recipients: + sijinjoseph, lemburg, terry.reedy, belopolsky, tim.golden, r.david.murray, brian.curtin, cm
2013-04-13 18:11:24	sijinjoseph	set	messageid: <1365876684.58.0.690479870915.issue17627@psf.upfronthosting.co.za>
2013-04-13 18:11:24	sijinjoseph	link	issue17627 messages
2013-04-13 18:11:24	sijinjoseph	create