Message170453
| Author |
ngie |
| Recipients |
ngie |
| Date |
2012年09月13日.19:02:46 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1347562967.67.0.94049562536.issue15942@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Windows doesn't return sane values for localtime(3) (per POSIX [1]) when
the BIOS is set to the local time (the host is a Win2k8-R2 machine):
$ python -V; python -c 'import time; print time.strftime("%m-%d-%y %H:%M:%S", time.localtime())'; date; uname -a
Python 2.6.1
09-13-12 19:56:03
Thu, Sep 13, 2012 11:56:03 AM
CYGWIN_NT-6.1-WOW64 QAQA-ORPTO8B466 1.7.11(0.260/5/3) 2012年02月24日 14:05 i686 Cygwin
This seems to be a conscious design choice on Microsoft's part:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms724961%28v=vs.85%29.aspx
I'll try and follow this up with the POSIX folks or maybe Microsoft, but
for the time being this needs to be documentation as an issue with downstream consumers (perl 5.8.9 also illustrates this issue). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年09月13日 19:02:47 | ngie | set | recipients:
+ ngie |
| 2012年09月13日 19:02:47 | ngie | set | messageid: <1347562967.67.0.94049562536.issue15942@psf.upfronthosting.co.za> |
| 2012年09月13日 19:02:47 | ngie | link | issue15942 messages |
| 2012年09月13日 19:02:46 | ngie | create |
|