On Wednesday 06 January 2010 16:55:30 Todd Blanchard wrote: > On Jan 6, 2010, at 1:57 AM, Diez B. Roggisch wrote: > >>>> Anyhow - any hints for how to extract the tw.dojo resources for static > >>>> deployment would be most welcome. > >>> > >>> tw.dojo tries something clever to allow deliverance of specific > >>> versions. To do so, it overrides JSLink & CSSLink in ways that seem to > >>> break the resource collection. > >> > >> So if I just go to site-packages and nuke the tw.dojo-0.9.8.1-py2.6.egg > >> directory it will go away and I can get back to using admin? I've tried > >> that and I cannot get admin to run in a mod_wsgi environment. It dies > >> horribly with some kind of resource error - even after nuking tw.dojo. > > > > I've switched from crystal balls to Ouija Boards, and have difficulties > > with the adaption. All it told me was "need stacktraces, logentries, > > sourcecode". Whatever that's supposed to mean. > > Here you go... > I'm having trouble making any sense of it myself. I've logged in and just > tried to hit /admin
I don't see anything even remotely TW-related in there. From what it looks, it appears that get_package_name() is misbehaving. I suggest you take a look at the fabulous documentation of Graham Dumpleton about using PDB with mod_wsgi. With that, you might shed some light on the issues. http://code.google.com/p/modwsgi/wiki/DebuggingTechniques Diez
-- 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.
