It's not clear from your OP what you mean by "dynamic choices" (I can still
provide a callable; is that not "dynamic"?)
Your best bet it to draw up a reproducible example (or even better a test
case) of exactly the behaviour that used to work but now doesn't.
I'd suggest putting that in a
>
> Fix of #24483 breaks possibility to declare dynamic choices for model's
> fields.
> I read the ticket and I understand the initial problem, but it was used
> frequently to support dynamic choices.
>
> Now we have always consistent but static choices, tests are passing,
> migrations have
Hi.
Fix of #24483 breaks possibility to declare dynamic choices for model's
fields.
I read the ticket and I understand the initial problem, but it was used
frequently to support dynamic choices.
Now we have always consistent but static choices, tests are passing,
migrations have consistent
