On Mon, 2007-03-12 at 11:53 -0300, Ramiro Morales wrote: > On 3/12/07, DavidA <[EMAIL PROTECTED]> wrote: > > > > I found a workaround but I'm not sure what the ramifications are. I > > commented out this line in django.conf.__init__.py: > > > > os.environ['TZ'] = self.TIME_ZONE > > > > What version/revision of Django are you using?. > > See ticket #2315 and changeset [4487] for some work donde > in the Windows time zone stuff front.
By the way, if anybody wants a fun little side project and enjoys doing Windows development, they could write some decent win32 timezone support stuff for us. There are obviously ways to do it (although the idea would be not to corrupt the whole server's idea of timezone -- just the current process), but it's not the same as the Unix world and so some specialist knowledge is required. Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
