[resend, reference included; sorrt for the noise] On Saturday 11 May 2013, Anssi Kääriäinen wrote: > > - While it might seem trivial to implement reload()/refresh() when > needed,
Indeed, it might; which is why I would assume many people have already done it. For these people, a new reload()/refresh() in core may go unnoticed or redundantly overridden. In the "test discovery" thread, Russel has mentioned an "upgrade checks" proposal[0] -- if it comes to fruition, and this ticket is reopened, I suggest that a check for pre-existing reoad/refresh methods on models be included in the upgrade check. Shai. [0] https://groups.google.com/d/msg/django-developers/0xuznNH7aP0/CCqyDTpWSj4J -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
