thanks for the offer, but as I said : the problem is long since solved. it was a circular import problem. I reworked the imports and its gone.
my question was: how could it have happened on the staging server and not on the dev server ? I was just asking around to see if anybody had seen that kind of behavior before and knew a likely explanation. and primarily how I can detect such problems in the future before I've deployed it to a live site. On Mar 8, 10:39 pm, Graham Dumpleton <graham.dumple...@gmail.com> wrote: > It is almost impossible to suggest anything about your problem as you > don't post the complete details of the actual errors you are getting. > If you want solutions, you need to provide that extra information so > we don't have to imagine what the Python exception and traceback you > are getting is. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
