Seems this issue was brought up several years ago, though the thread was later hijacked for other functionality and get_or_none fizzled out. https://groups.google.com/forum/#!topic/django-developers/Saa5nbzqQ2Q
In Django 1.6 there were convenience methods added for .first(), for the same principle of not having to catch an IndexError (or in this case, a DoesNotExist error); https://docs.djangoproject.com/en/dev/ref/models/querysets/#django.db.models.query.QuerySet.first This seems to be wanted by several users, as seen here; http://stackoverflow.com/questions/1512059/django-get-an-object-form-the-db-or-none-if-nothing-matches Seems to be quite an easy fix, just needs a proper patch. Any thoughts? Cal -- 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/CAHKQagEqGR%3DuPNhki1%3D%3DXjA7pT79ur-HJmGiaW%2B6ZdFdMXjt%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
