On May 30, 2010, at 5:43 PM, Hans Lellelid wrote: > I've griped about this before, but I think the biggest (only?) problem > that comes up repeatedly for us w/ Pylons is the inaccessibility of > these "special" globals from tests (without using response/request > objects). Stacked object proxies. I dream of a day (or a fork) when > these are either a thing of the past, or disabled by default. (Mike > has given me some pointers in the past, but I still maintain that > writing tests shouldn't be so hard. -- and one shouldn't be forced to > use the WebTest framework, which IMO is inadequate for services > applications.)
I've already put a changeset for this for 1.0.1 into the repo. app_globals and config will be completely available during unit tests when using the nose extension (as all Pylons projects do by default). Barring any other bugs reported, I'll release 1.0.1 to address this within the next week. Cheers, Ben -- 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.
