The few places I see Loggerhead use the datetime module, it uses datetime.datetime.fromtimestamp(some_utc_timestamp), which creates an object that uses the local time zone but doesn't know it. It's usually okay to have Loggerhead display times in local time with no time zone information, but the Atom feed needs to be aware of time zones, and that information is just not available from a "change" object.
What do you want to do? Least invasive would be adding "utc_date" and/or "timezone" attributes to "change" objects, but maybe it would be better to use UTC or the revisions' original time zones everywhere. Or continue using local time, but show the time zone in the UI. Or something; I dunno.
(By "change" objects I mean those returned by loggerhead.history.History.get_changes() and passed around everywhere.)
(Time zones and "datetime" make me want to bang my head on a wall.)
Edit: I meant to add, I don't know how much of the code base is effected by this, since, well, grepping for "datetime" only returns 3 results, but "time" returns...a lot more. :P Any solution may need to apply to other things as well.
It would be good to be less naive here.
I guess local-timezone-
I share the desire to bang my head on a wall when I think too hard about all this stuff though.