On 8 August 2013 09:31, Russell Keith-Magee <russ...@keith-magee.com> wrote:
> On Wed, Aug 7, 2013 at 8:10 PM, Daniele Procida <dani...@vurt.org> wrote: > >> On Wed, Aug 7, 2013, Aymeric Augustin <aymeric.augus...@polytechnique.org> >> wrote: >> >> >The main drawback of the current implementation is that it's impossible >> to >> >clear the cached value. That should be mentioned in the docs. >> >> Better still -- if we're going to formalise this as a public API, lets > update the implementation so that we *can* clear the cached value -- or at > least document the method by which one would clear the cache. Lets not > formalise a half-complete API :-) > I just ran some informal tests to compare it against my own "buffered_property" implementation, and "del x.foo" deletes the cached value just fine for me, as does "delattr(x, 'foo')". Next access calls the method again, as expected. Also "x.foo = 'test'" sets the value fine. After our discussion on IRC today, Russ, I'm confident the current implementation functions as you expect. > One suggestion -- a new special topic guide on performance tweaking, just > like we have for security. We've already got this page: > > https://docs.djangoproject.com/en/dev/topics/db/optimization/ > > which is all about database optimisation -- this is a big part of > optimising, but it's not the only story. A "performance" topic guide would > give a chance to introduce value caching, template loading options > (including cached templates), fast and slow session options, discussing how > and when the database is hit, as well as little performance tweaks like the > documented parts of utils.functional. > > Hmm... I think I might have a few ideas to throw into that pile :) > Russ %-) > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
