On 20 March 2014 08:58, Florian Demmer <[email protected]> wrote: > > > On Thursday, August 8, 2013 6:59:14 PM UTC+2, Łukasz Rekucki wrote: >> >> Hi, >> >> I have some minor nitpicks: >> >> 1. Unlike the standard @property, the current implementation of >> @cached_property doesn't allow for a docstring. >> 2. Calling `del obj.<cached_property_name>` before accessing the value >> or more then once in a row throws an AttributeError. >> >> Should I make a new ticket for that or just send a PR for the old one ? >> >> > wow, that AttributeError is super annoying to handle... i'd apprechiate a > patch for that if you have it already written! >
How is it behaving any differently to a normal attribute? I went through this a year or so ago with RKM - once the property is set, del will clear it, allowing you to affect the call again. But if it's unset, del will raise an AttributeError - just like any other attribute. -- Curtis -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAG_XiSCnEqqgqdrdMmadhc3RAOue2P%2Bv6d4WnK%2B5Eba2Tj7ajA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
