#24523: django.apps.registry.populate() does not handle failures in
app_config.ready()
-------------------------------+--------------------------------------
Reporter: kalium99 | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7
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 kalium99):
That's right, the `PartnerSelection` form is running database queries.
This situation is not ideal for a couple of reasons (not in the least that
the field is not updated until a process is recycled).
{{{
class PartnerSelection(forms.Form):
partner = forms.ChoiceField(label='Partner', choices=[ (p.id,
p.company_name)
for p in Partner.objects.all()])
}}}
So moving this (and anything similar) would solve this particular instance
of the problem, but not the underlying issue in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/24523#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.861143eb957222a1c1b7145cc9b65dec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
