On Fri, Mar 14, 2014 at 11:15 AM, Cal Leeming [Simplicity Media Ltd] < [email protected]> wrote: > > >> .get(or=None) (of some description) would be my preference, but even that >> is ugly and confuses the existing API with "special" keywords that aren't >> actually a filter. >> > > I would be strong -1 on having a special keyword. >
Even if the special keyword is 'default'? .get(..., default=None) is a common python pattern that fits well with this usage. Regards, Michael Manfre -- 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/CAGdCwBsUVMuvRqoHxcuXoJS%3Df1NVadedv90cx1vhWxuL70ZEdw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
