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"?
On Wednesday, June 20, 2012 7:57:34 PM UTC+4, Chris McDonough wrote: > > On 06/20/2012 11:55 AM, Max Avanov wrote: > > I wonder why pyramid documentation prefers one solution to another. If > > some method is objectively better than another, I would like to know it > > before I make a decision. > > It's discussed in the docs about get_current_registry and threadlocals. > You can read it and believe it, or not (it says something like "makes > testing harder and more fragile"). If you believe it, don't use > threadlocals. If you don't believe it or don't care, use them. > > - 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/-/ZmB9gWa-zkMJ. 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.
