Django 1.2.3 compatible with python 2.5.2 ? Weird django behaviour
By default mod_python decides when to reload, so you'll get what you get when you get it.
Maybe I am mistaken, but I thought there was a directive you could send that would explicitly force the python reload now.  That should (in theory) help with achieving consistent but perhaps not ideal, behavior.
Off topic, this sounds like a good opportunity to enhance your app's logging so you'll have better breadcrumbs to follow next time things hang.
Well main question of the day will django work correctly under python 2.5.2 ?
So why i am asking this question?
First of all  i have some test class written , nothing special which renders a page. The problem is that everytime i access this page i get random 3 different responses :
1)exceptions must be classes, instances, or strings (deprecated), not type
2) Http404 
3) page renders normally .
And generally i can refresh until i get the result i want , well in my case normally rendered page. I am a little bit confused what even to think . Because my written class does pretty much nothing.Just a test class to test some things.
I run Django 1.2.3 under python 2.5.2 on Debian .
Also what i noticed . I use PyCharm 1.1.1 through remote host with auto upload every time change is made , it uploads but somehow changes are not always applied after initial upload . What i mean is that it feels like files are not compiled ~~ if u can say it this way ...
What's teh chance that it has basically nothing to do with python and django O_O and that are some other weird bugz ?