[Python-Dev] RE: Bug in time.timezone of Python 2.1.1

[Norman Vine]

This is a multi-part message in MIME format.

------=_NextPart_000_0060_01C13713.5D269340
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Ivan J. Wagner writes:
>Sent: Thursday, September 06, 2001 8:03 PM
>To: cygwin@sources.redhat.com
>Cc: jason@tishler.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

------=_NextPart_000_0060_01C13713.5D269340
Content-Type: application/octet-stream;
	name="timemodule.diff"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="timemodule.diff"

*** timemodule.bak	Wed Jun 27 09:01:54 2001=0A=
--- timemodule.c	Thu Sep  6 20:29:28 2001=0A=
***************=0A=
*** 599,605 ****=0A=
  	/* Squirrel away the module's dictionary for the y2k check */=0A=
  	Py_INCREF(d);=0A=
  	moddict =3D d;=0A=
! #if defined(HAVE_TZNAME) && !defined(__GLIBC__)=0A=
  	tzset();=0A=
  #ifdef PYOS_OS2=0A=
  	ins(d, "timezone", PyInt_FromLong((long)_timezone));=0A=
--- 599,605 ----=0A=
  	/* Squirrel away the module's dictionary for the y2k check */=0A=
  	Py_INCREF(d);=0A=
  	moddict =3D d;=0A=
! #if defined(HAVE_TZNAME) && !defined(__GLIBC__) &&!defined(__CYGWIN__)=0A=
  	tzset();=0A=
  #ifdef PYOS_OS2=0A=
  	ins(d, "timezone", PyInt_FromLong((long)_timezone));=0A=

------=_NextPart_000_0060_01C13713.5D269340--