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.
On Wednesday, June 20, 2012 7:49:45 PM UTC+4, Chris McDonough wrote: > > On 06/20/2012 11:46 AM, Max Avanov wrote: > > It seems that pyramid.threadlocal.get_current_request() is the lesser > evil. > > Is there a rationale why should I prefer this verbose and complicated > > (semantically unclear) code sample to "strictly prohibited" > > get_current_request? > > You can do as you like, it's your software. > > - 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/-/TQQv8SNtOi4J. 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.
