Remy Blank wrote: > Christian Boos wrote: > >>> Tim, what version of pytz do you have on your test machines? >>> >> None I guess, as I see <FixedOffset "GMT +1:00" 1:00:00> in the test >> results, which is our own tzinfo subclass. >> > > That was also my guess, but I could reproduce the issue neither with nor > without pytz. > > If pytz is not installed, how could two Linux platforms have different > behaviors for this, if we only use our own timezone classes (which don't > use local TZ info)? It would basically mean that the datetime module, in > particular datetime.replace(), behaves differently. >
Right, look at time.daylight usage in the code. Tim's buildbot must live in a non-DST timezone. I suppose the test has to take this into account, for choosing an appropriate expected value. -- Christian -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
