On Friday, October 12, 2012 3:35:53 PM UTC+2, Chris Wilson wrote: > > I'm strongly in favour of a simple, obvious way to do the common thing, > which is to return None if the object doesn't exist, instead of throwing > an exception. My preferred method names would be .nget(), .get_or_none() > or .first(). >
IMHO the fact that we have all these inventive solutions is ample proof that people do come across this problem and find it annoying. I just found out today that there's a somewhat related .latest(). Anyway, without a sponsor with commit access I guess this is dead, so I'll shut up now. Thank you for your time. Ole -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/xFWfDQzuQ7cJ. 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.
