#34388: Added support for direct usage of Choices classes on model fields
-------------------------------------+-------------------------------------
Reporter: T. Franzel | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Wobrock):
* cc: David Wobrock (added)
Comment:
Hi,
Thanks for submitting this ticket. I like it from an API perspective, as
it adds a tiny bit of convenience, and I don't think the maintenance
burden is very high.
I left a few comments on the PR, but someone else will be needed to
approve this feature :)
> if it could still slip into 4.2
According to https://docs.djangoproject.com/en/4.1/internals/release-
process/#phase-three-bugfixes, since the beta for 4.2 is out, I think we
are already in the bug fixing phase :/
--
Ticket URL: <https://code.djangoproject.com/ticket/34388#comment:1>
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/01070186b73a7ebe-f8ea1e88-8bfe-4986-965f-eef5b5f50f9f-000000%40eu-central-1.amazonses.com.
