#17750: User.get_profile() returns cached object when database object has
changed
-------------------------------------+-------------------------------------
Reporter: rjalves | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* severity: Normal => Release blocker
Comment:
I was going to commit this and did some final polish, available from here:
https://github.com/akaariai/django/tree/ticket_17750
The reason I decided to wait is that the custom user model stuff is likely
going to land into Django soon. get_profile() is going to be deprecated,
so I am wondering if it is a good idea to do changes to already deprecated
features. In addition, I want to avoid messing in the same code areas to
make merging easier (even if this isn't a big problem in Git age).
I am marking this as Release Blocker - the reasoning is that I want us to
decide if we want this into 1.5 or not, and without this marker this is
likely going to be forgotten into the depths of Trac...
--
Ticket URL: <https://code.djangoproject.com/ticket/17750#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
