On Thu, Apr 07, 2005 at 11:22:39AM -0400, Paul Winkler wrote:
> Maybe this is relevant:
> http://www.zope.org/Collectors/CMF/325
>
> ... crap, I never merged the fix.
OK, now this is merged to the trunk and CMF-1_5-branch.
--
Paul Winkler
http://www.slinkp.com
On Thu, Apr 07, 2005 at 02:44:38PM +0200, Max M wrote:
> Max M wrote:
>
> >When I convert to DateTime objects, they are saved as "9:00 Universal".
> >So that is correct too.
>
> Ok. Turned out that I have misunderstood zopes DateTime().
>
> It saves in UTC, but it still needs a timezone.
>
> S
Max M wrote:
When I convert to DateTime objects, they are saved as "9:00 Universal".
So that is correct too.
Ok. Turned out that I have misunderstood zopes DateTime().
It saves in UTC, but it still needs a timezone.
So converting datetime objects to the local timezone and then converting
to DateT
Max M wrote:
I have a product where I convert some external datetimes to zope
DateTime() objects. I save them as UTC as zopes DateTime does by default.
But when these are rendered, the time is offset by two hours.
Ok. I was unclear here.
I convert from datetime objects (python) to DateTime (zope
