#30949: Use functools.cached_property instead of
django.utils.functional.cached_property.
-------------------------------------+-------------------------------------
Reporter: Thomas Grainger | Owner: David
Type: | Smith
Cleanup/optimization | Status: assigned
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mateusz Leszko):
Replying to [comment:2 Simon Charette]:
> FWIW `functools.cached_property` adds a `RLock` acquisition overhead for
thread safety which is not something needed by most internal Django's
usage and third party ones from my personal experience.
>
> If we were to proceed with this patch we should measure the impact of
this thread safety mechanism first and also document it.
Hi, I am trying to solve this issue, but is't it true that: if
`functools.cached_property` uses `RLock`, then we don't need to worry
about it, cause its python3 implementation and we can trust it?
--
Ticket URL: <https://code.djangoproject.com/ticket/30949#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.cb060bbcf2e336d61ab2306a03cdcd36%40djangoproject.com.
