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 mirkovogt
Recipients belopolsky, mirkovogt, r.david.murray
Date 2015-01-27.18:40:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422384016.54.0.181096103325.issue23332@psf.upfronthosting.co.za>
In-reply-to
Content
Actually I'm not sure anymore whether NOT specifying a timezone is valid at all.

Even though the Spidermonkey documentation itself states, that it doesn't behave according to the ISO standard, several documents say that specifying the timezone is crucial (either "Z" or "+/-XX:XX").

I also found documents describing the standard which explicitly state that by default the local time is assumed, as JavaScript does.

Either way - there's so much different information and therewith confusion out there, that I highly recommend always specifying the timezone and would consider behaving otherwise as a bug.

Implementations usually don't throw an error but just assume something when the TZ designator is missing, which results in just different meanings. Needless to say that doesn't make the situation any better.
History
Date User Action Args
2015-01-27 18:40:16mirkovogtsetrecipients: + mirkovogt, belopolsky, r.david.murray
2015-01-27 18:40:16mirkovogtsetmessageid: <1422384016.54.0.181096103325.issue23332@psf.upfronthosting.co.za>
2015-01-27 18:40:16mirkovogtlinkissue23332 messages
2015-01-27 18:40:16mirkovogtcreate