On 10 loka, 00:49, Michael Hudson-Doyle <mica...@gmail.com> wrote: > > OK, it seems .get_or_none() method is out. I can see the point of that > > decision, there are a lot of similar methods that could be added using > > the convenience argument (like .first() in conjunction > > with .latest()). > > > But, how about .get() with __default kwarg? > > My experience is that the _only_ default you will ever use in this > situation is None.
Good point - it seems all usages of __default with non-None values would be abuse of the API. So, maybe the kwarg could be named '__allow_none' or something along those lines? > FWIW, get_or_none() seems useful to me but I can live without it. For the record: that is my take on this, too. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
