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 v
Thanks. I am on trunk, 4227 so I don't have this fix.
On Mar 12, 10:53 am, "Ramiro Morales" <[EMAIL PROTECTED]> 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__.
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 [
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
On Mar 12, 10:19 am, "DavidA" <[EMAIL PROTECTED]> wrote:
> I have some scripts that run tasks and use Django DB models. They have
> been r
I have some scripts that run tasks and use Django DB models. They have
been running an hour late today after all the DST changes (here in the
US). I've traced it down to any call to Django is shifting my time
back an hour (like it was before this weekend's shift).
So the time as reported by time.
5 matches
Mail list logo