DateTime uses UTC as default Timezone if none given
Bug #378616 reported by
Estartu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DateTime |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
We upgraded our System recently from Zope2.9 to Zope2.11. Under Zope2.9 print DateTime(
I know that there was some work done to get DateTime working with timezones correctly.
I have patched DateTime.py to use the Local Timezone when no timezone is given in iso8601 format.
I have atteched this patch to this Bugreport.
In Order to provide compatibility to the Old behavior the patch can be activated with a zope.conf directive.
affects: | zope2 → datetime |
To post a comment you must log in.
Well... isn't this because it now supports timezone naive datetimes? In which case the new behaviour makes sense?
In any case I think it's a bad idea to have this a configuration setting. You'll change the way othe peoples software behaves. A parameter is better in that case.
I also think fiddling with DateTime is a generally bad idea. DateTime is a dead end, we should only change it if it has proper bugs, not because we want a different type of behaviour.