You don't say anything about what hosting mechanisms you are using for each.
The Django runserver does extra automagic setup steps which aren't by default going to be done by other hosting mechanisms. Part of this is solved by manual setup of sys.path, but not necessarily all that is necessary. Hosting mechanisms may also not run as same user as when you run Django runserver by hand, so you need to deal with user permissions and file system permissions. Graham On Mar 8, 10:00 am, felix <crucialfe...@gmail.com> wrote: > I have two identical django deployments and one of them (the beta > staging server) is having import errors on startup and is failing. > > 1. is something causing the deployments to be loading classes in > different orders ? > > the directory structure is identical, the pythonpaths are in an > identical order. I tried removing the *.pyc files > > There's probably some minor difference in the setups, and I'll find it > soon. > > But more importantly I need to know for the future how I can detect > test the codebase on the new server before restarting on a live > website. > > 2. is there a good way I can load the app as the server will load it > (WSGIHandler) and thus discover the errors before I've restarted the > web ? > > manage.py shell loads fine. I can do the same import that failed. I > can run admin.autodiscover() > > thanks for any tips, -- 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.
