Hey Mariusz, thanks for the link — I found some other threads but not that one. Would you mind saying why you're personally against it (`get_or_none` specifically)?
At least how I read that thread, there was more debate about how to add it than whether to add it at all, and then Cal sort of "gave up" by suggesting a docs patch that I'm not sure ever happened anyway. I don't want to kick off a huge thing about it, but that one was 8 years ago and, like you said, it has come up a number of times over the years (maybe that's normal). Thanks! Dave On Wednesday, July 6, 2022 at 11:35:36 PM UTC-5 Mariusz Felisiak wrote: > Hi, > > Adding `get_or_none()` was discussed several times and was always > rejected. This thread > <https://groups.google.com/g/django-developers/c/h50RLblVDU8/m/vuffkI2aylgJ> > has a nice summary. Personally, I'm still against it. > > Best, > Mariusz > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/46daf75f-bb6b-457a-8889-47b148b20d61n%40googlegroups.com.
