Another option that hasn't come up is to just have a custom __setattr__ that won't let users write to self (therefore providing primitive thread safety). I don't think it is a /good/ option, but I am just throwing it out there for completeness.
_Nick_ On Tue, Jun 15, 2010 at 7:10 AM, Patryk Zawadzki <pat...@pld-linux.org>wrote: > If you don't mind, I'll talk a bit more to myself. > > On Tue, Jun 15, 2010 at 3:38 PM, Patryk Zawadzki <pat...@pld-linux.org> > wrote: > > I really don't think we should add anti-moron filters at the framework > > level past documenting "taking care to ensire immutability of view > > instances". > > This came out a bit harsh. What I mean is: teach users how to write > thread-safe views (classes or not) and ignore those who refuse to do > it. They either know what they're doing or there is really no point in > forcing the help upon them. > > -- > Patryk Zawadzki > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
