Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 7 Sep 2001 14:05:45 -0700 (PDT) From: "Ivan J. Wagner" X-Sender: wagner17 AT sslnet DOT com To: Norman Vine cc: cygwin AT sources DOT redhat DOT com, jason AT tishler DOT net, python-dev AT python DOT org Subject: RE: Bug in time.timezone of Python 2.1.1 In-Reply-To: <005f01c13734$e4383340$a300a8c0@nhv> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Norman, Thanks a lot for the patch. I just tested it out and it fixed the problem. On Thu, 6 Sep 2001, Norman Vine wrote: > Ivan J. Wagner writes: > >Sent: Thursday, September 06, 2001 8:03 PM > >To: cygwin AT sources DOT redhat DOT com > >Cc: jason AT tishler DOT net > >Subject: Bug in time.timezone of Python 2.1.1 > > > > > >I maintain a CVS archive (using cvs 1.11.0-1) on a Cygwin 1.3.2 install > >and use ViewCVS 0.7 to access it. ViewCVS uses python and today I > >upgraded from python 2.1-1 to 2.1.1-1. However the upgade > >broke the Age > >field in ViewCVS. The Age field is the time span between the > >file's check > >in and today. The Age field is displayed when you view a CVS directory > >listing. I looked at the ViewCVS sources and tracked the problem to > >time.timezone. In 2.1 it returns 18000 but in 2.1.1 it returns > >1834228892. Does anybody have any day what might be causing > >this problem? > > > >Thanks, > >Ivan Wagner > > YES > > see attached patch > > Cheers > > Norman Vine > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/