2008/11/5 Max Ischenko <[EMAIL PROTECTED]>: > > >> # ADD >> import django.conf >> django.conf.settings._import_settings() >> >> I think this will force import settings module before Pylons >> configured. If that works, then perhaps move it after Pylons >> initialisation and see what is different. > > Yes, this solved it.
If you ever find out what Pylons might be doing to sys.path or whatever else it is changing to cause lazy importing not to work, please let us know. At least have a work around. > I actually got it working more or less, > http://dpaste.com/hold/88846/ > > It sets up Pylons middleware in through WSGI and my Django app can > actually use pylons.c, pylons.g, h.url_for() and other stuff. > > Your help was invaluable, thanks! I still have to tweak Apache setup > according to your guidelines so I'll get back later. Those suggestions of splitting Django/Pylon probably no longer relevant then. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
