But why view_config cannot accept a tuple of decorators? On Wednesday, June 20, 2012 8:24:30 PM UTC+4, Chris McDonough wrote: > > On 06/20/2012 12:14 PM, Max Avanov wrote: > > I don't used to blindly believe something just because it was written > > that way. The docs are not just a collection of essay about web > > development. It should be explanatory and clear. That is their main > purpose. > > I came to Pyramid after three years of Pylons-based web development. It > > wasn't hard to test pylons-based applications. So, why the > > get_current_request "makes it possible to write code that can be neither > > easily tested nor scripted"? > > Here's a presentation about API design I wrote recently, part of which > discusses why using thread locals are often a bad idea: > > https://github.com/mcdonc/apidesign/blob/master/presentation.rst > > But I probably test differently than you do, and have different > development practices than you. In particular, I probably treat my > applications more like libraries than you do, and write more unit tests > than functional tests. Thread locals tend to suck when you write actual > unit tests or you need to reuse code outside of the request/response > context. > > - C >
On Wednesday, June 20, 2012 8:24:30 PM UTC+4, Chris McDonough wrote: > > On 06/20/2012 12:14 PM, Max Avanov wrote: > > I don't used to blindly believe something just because it was written > > that way. The docs are not just a collection of essay about web > > development. It should be explanatory and clear. That is their main > purpose. > > I came to Pyramid after three years of Pylons-based web development. It > > wasn't hard to test pylons-based applications. So, why the > > get_current_request "makes it possible to write code that can be neither > > easily tested nor scripted"? > > Here's a presentation about API design I wrote recently, part of which > discusses why using thread locals are often a bad idea: > > https://github.com/mcdonc/apidesign/blob/master/presentation.rst > > But I probably test differently than you do, and have different > development practices than you. In particular, I probably treat my > applications more like libraries than you do, and write more unit tests > than functional tests. Thread locals tend to suck when you write actual > unit tests or you need to reuse code outside of the request/response > context. > > - C > On Wednesday, June 20, 2012 8:24:30 PM UTC+4, Chris McDonough wrote: > > On 06/20/2012 12:14 PM, Max Avanov wrote: > > I don't used to blindly believe something just because it was written > > that way. The docs are not just a collection of essay about web > > development. It should be explanatory and clear. That is their main > purpose. > > I came to Pyramid after three years of Pylons-based web development. It > > wasn't hard to test pylons-based applications. So, why the > > get_current_request "makes it possible to write code that can be neither > > easily tested nor scripted"? > > Here's a presentation about API design I wrote recently, part of which > discusses why using thread locals are often a bad idea: > > https://github.com/mcdonc/apidesign/blob/master/presentation.rst > > But I probably test differently than you do, and have different > development practices than you. In particular, I probably treat my > applications more like libraries than you do, and write more unit tests > than functional tests. Thread locals tend to suck when you write actual > unit tests or you need to reuse code outside of the request/response > context. > > - C > On Wednesday, June 20, 2012 8:24:30 PM UTC+4, Chris McDonough wrote: > > On 06/20/2012 12:14 PM, Max Avanov wrote: > > I don't used to blindly believe something just because it was written > > that way. The docs are not just a collection of essay about web > > development. It should be explanatory and clear. That is their main > purpose. > > I came to Pyramid after three years of Pylons-based web development. It > > wasn't hard to test pylons-based applications. So, why the > > get_current_request "makes it possible to write code that can be neither > > easily tested nor scripted"? > > Here's a presentation about API design I wrote recently, part of which > discusses why using thread locals are often a bad idea: > > https://github.com/mcdonc/apidesign/blob/master/presentation.rst > > But I probably test differently than you do, and have different > development practices than you. In particular, I probably treat my > applications more like libraries than you do, and write more unit tests > than functional tests. Thread locals tend to suck when you write actual > unit tests or you need to reuse code outside of the request/response > context. > > - C > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/7ShbVQOxIAIJ. 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.
