On 30/01/2008, Lukasz Szybalski <[EMAIL PROTECTED]> wrote: > > From what I can tell you have called a sub application of your site > > the same name as the site. This to me would seem to be a very bad idea > > because depending on how the Python module search path is defined all > > sorts of weird things could happen. > > > > This may actually be the cause of all your problems, so don't call > > your sub application the same name as your site, call it something > > different and start over again. > > > > After reading this I have tested it and it didn't make a difference, > but when I tested it today it DOES work. It had to be late the last > time or something. > Ok as long none of the functions/sub apps have the same name as my > webpath app name then we should be good. > > Can I move /usr/lib/apache2/modules/mod_wsgi.so to my production > server? This file was compiled on Intel duo, and my server is amd > based? Both x86. If yes then there would be no need to install the > extra dev packages on the server as debian stable doesn't have the > package available yet (debian testing does apt-get install > libapache2-mod-wsgi)
As long as they are same OS distribution, Apache major/minor version (preferably close patch revision) and Python major/minor version. Also would need to have been compiled as x86 and not x86_64 or amd64 as the later two might see specific instructions for those CPU types being used. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
