#24723: Errors while squashing migrations should be more informative
--------------------------------------+------------------------------------
Reporter: yarbelk | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords: Migrations, Exceptions
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
When squashing a set of migrations, the errors should be a bit more
informative - such as
giving a file/line number to where the originating offensive code is
An example is ValueError 'Cannot serialize function: lambda'
https://github.com/django/django/blob/1.7.7/django/db/migrations/writer.py#L360
- Note - I couldn't easily figure out what is being done here because the
method is a bit long to keep context in my head. I'm not sure if you have
access to this information in this method.
--
Ticket URL: <https://code.djangoproject.com/ticket/24723>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.c1af1bf15eaa0c3696747bf0df12752a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
