Mysterious thread problem

Hello all,

I use Windows XP, MySQL 4.1 and Django trunk version. Until
yesterday
everything worked fine, but now I have really weird thread
problem with
django's own developement server. Eventually pages are
shown correctly,
but it's rather rare than rule, and sometimes some images
or css-files
does not reach to browser.

Yesterday I had this problem with one of my projects and not
with
others, and I managed to solve it with rewriting the
project's
settings.py. Today I have the same problem with one other
project and
not with the one I had  yesterday. And now the rewriting of
settings.py
does not help.

The developement server restarts itself after every request
and some
times it prints out the following error message:


Unhandled exception in thread started by
Error in sys.excepthook:

Original exception was:
Validating models...
0 errors found.


Any clues would be greatly appreciated.

TT

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Yip, we had the same problem, it's to do with the time
change that
happened 2 days ago. To cut a long story short, set the
timezone in
your settings file to TIME_ZONE = ""
Django will then use the timezone returned by windows.

The problem is that in django.conf.settings.py, line 64, it
sets the TZ
variable. The timezone it tries to set is from the postgres
database,
i.e. the link given in the settings file. These however are
not valid
for mysql, so mysql resets it to GMT. So, the thread
reloads, thinking
that the timestamp for a file has changed. And it keeps
doing it over
and over.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Thanks a lot, didn't thought about that in the first place


yuri kirjoitti:
> Yip, we had the same problem, it's to do with the time
change that
> happened 2 days ago. To cut a long story short, set the
timezone in
> your settings file to TIME_ZONE = ""
> Django will then use the timezone returned by windows.
> 
> The problem is that in django.conf.settings.py, line
64, it sets the TZ
> variable. The timezone it tries to set is from the
postgres database,
> i.e. the link given in the settings file. These however
are not valid
> for mysql, so mysql resets it to GMT. So, the thread
reloads, thinking
> that the timestamp for a file has changed. And it keeps
doing it over
> and over.
> 
> 
> 
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---