#28492: Allow defining expressions' default output_field as a class attribute
rather than in __init__()
-------------------------------------+-------------------------------------
Reporter: Mads Jensen | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"08654a99bbdd09049d682ae57cc94241534b29f0" 08654a99]:
{{{
#!CommitTicketReference repository=""
revision="08654a99bbdd09049d682ae57cc94241534b29f0"
Fixed #28492 -- Defined default output_field of expressions at the class
level.
This wasn't possible when settings were accessed during Field
initialization
time as our test suite setup script was triggering imports of expressions
before settings were configured.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28492#comment:3>
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/068.a2eceec4534cf65ea18956feca71abcd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
