I'm sorry to add a "me too!" to this thread (instead of an answer), but this is by far the most frustrating thing about Pylons (well, Paste...). In fact it's one of the only really frustrating things about Pylons. I hate the stacked object proxies. They are completely useless for us and cause _so much_ pain for unit testing. Can't we please just have thread-locals?! I can only assume from the sorry state of testing support in Pylons/Paste that no one is doing it. (And the WebTest stuff really only applies for the most basic applications, which are not the ones we are using Pylons to build.)
Hans On Jul 1, 5:41 pm, Yang Zhang <[email protected]> wrote: > When attempting various things from our unit tests, such as calling > render_mako or calling pylons.url or looking up certain parameters in > pylons.config, we've run into problems with the environment not being > fully set up, such as "No object (name: tmpl_context or C) has been > registered for this thread". > > So far, we've been reading through the pylons source and then hacking > our way around each problem, such as by calling directly into mako's > render method or manually calling pylons.config._push_object. Is there > a better way to get a non-crippled environment in our tests? Thanks. > -- > Yang Zhanghttp://yz.mit.edu/ -- 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.
