> the request cycle is not getting confused. Ha! O.k. I think it's pretty clear who is confused. :)
Graham, your 'spurious_example()' bit really helped the lights go on. Of course it's obvious to me now (return self.foo() instead of call self.foo()) but sometimes you need to 'talk' it out to see the errors of your ways. Appreciate the discussion, almost feel like there could be a 'Friday Foibles' column (*ing yrs truly!). Hope people don't mind the blather but I really enjoy and learn and am indebted to 'the list'. Fwiw, this is a login process, but the more general pattern at play here, as I see it, is foo() having to get a foreign key for a primary table in bar(), and having to (o.k., I'll say it) redirect from bar() to foo() if the foreign key is not present. nxt up - my own web framework! (joke ;) -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
