X-Spam-Check-By: sourceware.org Message-ID: <44671C44.7050309@t-online.de> Date: Sun, 14 May 2006 14:02:12 +0200 From: Christian Franke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Python 2.4.1-1 time.altzone does not include DST offset Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ID: TluYKGZVYe-nMmDxz3SM9KO2FerrrmhaU3uxi4duNG7ARnB0n7oMsk X-TOI-MSGID: ef98ba77-1e5b-48a1-af73-cace6f6b6968 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Python's time.altzone is equal to time.timezone, it should be time.timezone-3600 (for CEST) $ python -c 'import time; time.tzset(); print time.ctime(), \ time.daylight, time.timezone, time.altzone, time.tzname' Sun May 14 13:46:55 2006 1 -3600 -3600 (' ', ' ') Possible side effect of the blank and equal tzname strings (caused by the timezone names returned by german XP) ? Cygwin's runtime timezone offset looks good: $ date '+%c %z "%Z"' Sun May 14 13:46:55 2006 +0200 " " This possible python runtime bug causes bad time conversions in rdiff-backup-1.1.5 ([Maybe ITP] ;-) Christian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/