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 rbp
Recipients Rodolpho.Eckhardt, belopolsky, docs@python, fdrake, henriquebastos, rbp, techtonik, tim.peters
Date 2010-11-20.20:46:25
SpamBayes Score 7.634178e-09
Marked as misclassified No
Message-id <1290285987.11.0.774107757231.issue9305@psf.upfronthosting.co.za>
In-reply-to
Content
1. Done (it's on the patch I'm uploading). Sorry.

3. Ok, we've rewritten that sentence. As Henrique mentioned, we're working on a larger patch to make datetime documentation clearer, and we can include a definition of "standard time" there.


2. I assume you're talking about sentences like "(negative for west of UTC)". We removed that wording because it inevitably leads to associating UTC with a geographical reference. Even if we disregard that, it's not true that "utcoffset is negative west of UTC", since it will we zero for for UTC-1 (and even +1 for places physically "west of UTC" but at timezone UTC+0) when DST is effective.

It seems that any sentence we add to that effect will be simply restating the definitions of UTC, timezones and DST (and their mathematical relationships). That is, "utcoffset will be negative when dt.tzinfo + dst() is negative".

Perhaps we could include a more detailed discusion about the sign of utcoffset() on the larger doc patch I've mentioned? Or do you have any suggestions?
History
Date User Action Args
2010-11-20 20:46:27rbpsetrecipients: + rbp, tim.peters, fdrake, belopolsky, techtonik, docs@python, henriquebastos, Rodolpho.Eckhardt
2010-11-20 20:46:27rbpsetmessageid: <1290285987.11.0.774107757231.issue9305@psf.upfronthosting.co.za>
2010-11-20 20:46:25rbplinkissue9305 messages
2010-11-20 20:46:25rbpcreate