#29970: Using cached_property on a model fails with: "Cannot use cached_property
instance without calling __set_name__() on it."
-------------------------------------+-------------------------------------
Reporter: Collin Anderson | Owner: Sergey
| Fedoseev
Type: Bug | Status: closed
Component: Utilities | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a68ea231012434b522ce45c513d84add516afa60" a68ea23]:
{{{
#!CommitTicketReference repository=""
revision="a68ea231012434b522ce45c513d84add516afa60"
Fixed #29970, #30041 -- Made ModelBase.__new__() pass attrs without
contribute_to_class() to type.__new__().
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29970#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.e9c4f2e10ae02d9d1cb0524ecc337bf9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
