#34710: Infinite migrations using models.Choices
-------------------------------+--------------------------------------
Reporter: Div Shekhar | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by David Sanders):
Hi Div Shekhar,
In order to get your example working you'd need to specify the type like
so:
{{{
class CoinTossResult(models.Model):
class CoinFace(str, models.Choices):
...
}}}
I don't think this is an issue with Django – though there may be some
documentation updates that could make this clearer when defining custom
`Choices` classes. I'll leave it up to felixx or nessita to decide whether
this ticket is invalid 😊
--
Ticket URL: <https://code.djangoproject.com/ticket/34710#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/010701894f1d48f6-83b385e3-b26f-4eb5-af6e-da37bad1e2db-000000%40eu-central-1.amazonses.com.
