#26214: Better error message for RuntimeError: populate() isn't reentrant
-------------------------------------+-------------------------------------
Reporter: Thomas Güttler | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: 1.9
Severity: Normal | Resolution: wontfix
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 Adrian Torres):
Is there a way that we can reopen this ticket? It's still a constant issue
and debugging the actual root cause of the issue can prove to be
problematic in remote environments, the linked solution in StackOverflow
has over 100k views which just goes to show how many people have run into
this issue and still do.
Don't know why Aymeric mentions Python 3's exception chaining by default,
it clearly does not happen here, at least not when executing commands such
as `python3 manage.py migrate`.
--
Ticket URL: <https://code.djangoproject.com/ticket/26214#comment:7>
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/010701840f90e896-646082ed-56e3-4d11-916f-ed9a9156f09e-000000%40eu-central-1.amazonses.com.
