Hi all,
I've had this sat in my drafts for a while. Rather than let it sit on the
shelf any longer I thought it better to share.
I've been thinking about recognising contributions recently. The main issue
with the notes here is that it focuses on code rather than contributions to
the wider
Thanks Adam! That makes sense to me - I believe Redis transactions are
atomic by default so the `cas` method wouldn't apply there. I took a look
at the LocMemCache code, and I think that the need for cas in this instance
also doesn't exist - because the code uses a threading Lock() to prevent
r
pymemcache also supports a cas() method, so that's two backends that could
have the other method.
I think the main problem is as Russell highlighted - supporting other
backends. It would be nice to see research into emulating cas(), at least
on LocMemCache which is often used as a fake during test
Hi all,
In https://code.djangoproject.com/ticket/30653 a feature request was made
to support annotating instances with an entire queryset. This was closed
wontfix because you can do this with the prefetch_related mechanism.
However, prefetch_related is very limited due to the design intention
Am 28.06.21 um 10:44 schrieb 'Adam Johnson' via Django developers
(Contributions to Django itself):
> Plus, it's not *that* much code to "take inspiration from" in your own
> project, test, and change as you see fit.
That's true...
;-)
--
Dr. Christian González
https://nerdocs.at
--
You re
