[Bug 711541] Re: time module in python 2.6 not working correctly.

Launchpad Bug Tracker 711541 at bugs.launchpad.net
Sat Jul 30 00:45:12 UTC 2011


This bug was fixed in the package python2.6 - 2.6.7-3ubuntu1

---------------
python2.6 (2.6.7-3ubuntu1) oneiric; urgency=low

  * Regenerate debian/control for Ubuntu

python2.6 (2.6.7-3) unstable; urgency=low

  * Make the conflict against python-profiler a versioned conflict.
  * Don't run the bsddb3 tests on kfreebsd-*.
  * Don't run the benchmark on hurd-i386.
  * Treat Linux 3.x as Linux 2. Closes: #633015.
  * Revert the suggested patch for issue #762963. LP: #711541.
  * Don't add the bsddb multilib path, if already in the standard lib path.
 -- Scott Kitterman <scott at kitterman.com>   Fri, 29 Jul 2011 20:41:23 -0400

** Changed in: python2.6 (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python2.6 in Ubuntu.
https://bugs.launchpad.net/bugs/711541

Title:
  time module in python 2.6 not working correctly.

Status in “python2.6” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: python2.6

  Description:    Ubuntu 10.10
  Release:        10.10

  python2.6:
    Installed: 2.6.6-5ubuntu1
    Candidate: 2.6.6-5ubuntu1
    Version table:
   *** 2.6.6-5ubuntu1 0
          500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
          100 /var/lib/dpkg/status

  As far as I'm aware, I have all timezone information on my system correct;
  I've run 'dpkg-reconfigure tzdata' to set my timezone properly.

  I have a simple script that demonstrates the problem:

  import os, time
  os.environ['TZ'] = 'US/Mountain'
  time.tzset()

  # Output the time with correct DST string:
  # date is (July 4, 2010)
  print(time.strftime('%c %Z', time.localtime(1278260625)))

  The expected result is:
  Sun Jul  4 10:23:45 2010 MDT

  The actual result is:
  Sun Jul  4 10:23:45 2010 MST

  (MST/MDT) is not being reported properly in Ubuntu/Debian.

  This problem only seems to exist in Python 2.x (at least for the
  package I have installed).  If I run the same script with python3, the
  correct MST/DST is returned.

  On a similar note, I've run the same test code on:
  Debian (sid): same results as ubuntu 10.10
  openSUSE 11.3:  Correct results (python-2.6.5-3.3.1.x86_64.rpm)
  SLES 11: Correct results  (python 2.6.0)
  gentoo:     correct results (python 2.6.2)
  RHEL 5.5:  Correct results (python 2.4.3)
  OS X 10.6.6:  Correct Results (python 2.6.6)

  I'm certain the problem is not with the code because it runs on every
  non-debian based system I've tried.  The problem also exists for a
  'default' ubuntu install, so I doubt it's a system configuration
  issue.

  My 'tzdata' package is 2010o-0ubuntu0.10.10

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: python 2.6.6-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Feb  1 15:17:43 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: python-defaults

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/711541/+subscriptions




More information about the foundations-bugs mailing list