#25154: Migration errors don't contain enough information to debug properly
------------------------------+--------------------------------------
Reporter: brandonmoser | Owner: nobody
Type: New feature | Status: new
Component: Migrations | 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 brandonmoser):
Replying to [comment:2 timgraham]:
> I am not sure if such a generic exception reporting mechanism is
feasible and/or practical to implement. Did you have any ideas about that?
>
> I typically use pdb inside Django's source code to get the needed
information.
As for exact implementation, I'm not sure. I'm pretty new to Python/Django
and haven't used pdb yet (I'll be digging into that next). I think the
frustration that I've seen in other tickets is that this is a failure
following a generated migration. If I had created a migration manually,
then I'm ok with obscure errors, since I should have a better
understanding of what I'm doing.
Here's what I would have liked to have seen in the error:
{{{
AttributeError: 'VersionedManyToManyField' object has no attribute
'_m2m_reverse_name_cache'. Seen on line 257 in
app_name/0003_auto_20150721_1018.py.
}}}
'''OR'''
{{{
AttributeError: 'VersionedManyToManyField' object has no attribute
'_m2m_reverse_name_cache' on `model_name.field`
}}}
Unfortunately for me, I've been fighting migrations for the last couple
days (due to some complicated changes) and have had to deal with errors
like this.
--
Ticket URL: <https://code.djangoproject.com/ticket/25154#comment:3>
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/070.e97a78b80efaece6817b8a23cffe5d0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
