Hi,

On Thu, Mar 27, 2014 at 1:03 AM, Willmer, Alex (PTS) <[email protected]> wrote:
> I’m not sure what to make of this, whether it’s a bug, fragile tests, and
> expected failure, or something else?
>
> Three unit tests fail in latest trunk (r12624 on Ubuntu 13.10/Python 2.7.5,
> set to the UK timezone. It appears that trac.util.to_datetime() returns a
> datetime object that is 1 hour ahead of that returned by
> datetime.fromtimestamp() when a timestamp is provided.
>
> I should mention that in January 1970 UK wall clock time was 1 hour ahead of
> UTC. This was changed in October 1971, since then the UK has been on GMT
> (UTC+0) during winter months.

Thanks for the reporting.

Reproduced with Trac 0.12-stable branch. It seems to be a defect.
Would you please create a new ticket for the issue at
http://trac.edgewall.org/newticket?

$ git status -sb
## 0.12-stable
$ TZ=Europe/London ~/venv/py24/bin/python setup.py test -s
trac.util.tests.datefmt.suite
...
FAILED (failures=3)
$ TZ=GMT ~/venv/py24/bin/python setup.py test -s trac.util.tests.datefmt.suite
...
OK
$ TZ=Europe/Berlin ~/venv/py24/bin/python setup.py test -s
trac.util.tests.datefmt.suite
...
OK

-- 
Jun Omae <[email protected]> (大前 潤)

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to