On Mar 9, 9:50 am, felix <crucialfe...@gmail.com> wrote: > 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 ?
As I said before, it is impossible to say as you provided insufficient detail. > 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. As I suggested before, consider doing some measure of development on the same hosting mechanism as you intend to deploy with. The Django runserver does magic stuff which other hosting mechanisms don't, including preloading and special importing of modules before any requests arrive. It is arguable that it should not do this, or that Django should provide a better WSGI entry point for WSGI hosting mechanisms, that ensures that the same level of presetup is done to mirror what runserver does. If this isn't done, you are always going to end up with subtle differences that have to be dealt with. Graham > 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.
