[issue17627] Datetime and time doesn't update timezone in a running Win app

Sijin Joseph added the comment: Some more links discussing similar issues http://www.sourceware.org/bugzilla/show_bug.cgi?id=154 - tzset not called frequently enough by localtime() and friends http://stackoverflow.com/questions/12150651/library-code-for-dynamically-reloading-the-usr-share-zonei

[issue17627] Datetime and time doesn't update timezone in a running Win app

Sijin Joseph added the comment: 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

[issue17627] Datetime and time doesn't update timezone in a running Win app

R. David Murray added the comment: On linux, if you call time.ctime() before and after changing the system /etc/localtime file, the time will be updated without restarting Python. The same applies to datetime.now(). -- nosy: +r.david.murray stage: needs patch ->

[issue17627] Datetime and time doesn't update timezone in a running Win app

Terry J. Reedy added the comment: I am not sure this is a bug, as I don't think it reasonable to expect every time function call to re-initialize the timezone setting. I think you should change this to a request to see if time.tzset can now be made to work on Windows and not unix-only (as docu

[issue17627] Datetime and time doesn't update timezone in a running Win app

Changes by Brian Curtin : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue17627] Datetime and time doesn't update timezone in a running Win app

New submission from CM: On Windows (tested on XP), the datetime module (and, as reported online in [1], time module) apparently gets the timezone only when a Python instance first starts, but then never updates the timezone during the life of that Python instance. So, if the user changes the