Re: Thread safety with view arguments in class based views

2012-05-17 Thread akaariai
On May 18, 12:17 am, Rafael Durán Castañeda wrote: > I'm wondering if this is suitable for a doc bug report, it is? I think a direct github pull request is the way to go. And yes, the docs could be clarified here. - Anssi -- You received this message because you

Re: Thread safety with view arguments in class based views

2012-05-17 Thread Rafael Durán Castañeda
El 17/05/12 22:11, Chris B escribió: Alright. That makes sense. Thanks everyone On Wednesday, May 16, 2012 4:18:49 PM UTC-7, Chris B wrote: According to the docs on the generic class based views : Each request

Re: Thread safety with view arguments in class based views

2012-05-17 Thread Chris B
Alright. That makes sense. Thanks everyone On Wednesday, May 16, 2012 4:18:49 PM UTC-7, Chris B wrote: > > According to the docs on the generic class based > views > : > >> Each request served by a >>

Re: Thread safety with view arguments in class based views

2012-05-17 Thread Rafael Durán Castañeda
El 17/05/12 04:51, Jon Paugh escribió: That last part refers to the way /Python/ handles arguments and the like. Whenever you have a complex object, such as an array, Python does not make a new copy of the object each time the view function is called. Instead, it passes a reference to the

Re: Thread safety with view arguments in class based views

2012-05-16 Thread Jon Paugh
That last part refers to the way *Python* handles arguments and the like. Whenever you have a complex object, such as an array, Python does not make a new copy of the object each time the view function is called. Instead, it passes a reference to the object, which means that if you change that

Thread safety with view arguments in class based views

2012-05-16 Thread Chris B
According to the docs on the generic class based views : > Each request served by a > View > has > an independent state; therefore,