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 Zhang http://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.
