#23816: Ability to defer model field by default
-------------------------------------+-------------------------------------
Reporter: Robert Coup | Owner:
| Denis.Tarykin
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
This ticket was tentatively accepted and we have several opinions against
its implementation ([https://code.djangoproject.com/ticket/23816#comment:4
Carl],
[https://github.com/django/django/pull/14110#pullrequestreview-610972680
Simon],
[https://github.com/django/django/pull/14110#issuecomment-830777943 Adam],
we can add me to this list).
Marking as "wontfix", because it seems we need to reach a consensus on the
DevelopersMailingList before moving forward. Please
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow the triaging guidelines with regards to
wontfix tickets] and take this to DevelopersMailingList to reach a wider
audience and see what other think.
--
Ticket URL: <https://code.djangoproject.com/ticket/23816#comment:12>
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/063.ed4d090ddf57201b48fc7963110b1e11%40djangoproject.com.
