After more time debugging than I care to admit, I realized an unexpected 404 was being caused by a form handler missing an expected argument. From a web server POV this makes perfect sense once I realized what was going on. What I'm wondering though is if there's a way to customize this behavior to throw an error in a development environment?
Thank you, Sam Justice -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
