#25370: Error display when makemigrations' field serializing fails with
ValueError
-------------------------------------+-------------------------------------
Reporter: torstenrudolf | Owner: Craig
Type: | Smith
Cleanup/optimization | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
It looks that it's not feasible to get `<app label>.<model name>.<field
name>` or even `<app label>.<model name>` in a reliable way because Django
serializes instances of `field`s from `django.db.models` not a model
attributes. Each approach doesn't work in some cases, e.g. constructing
messages in the `FunctionTypeSerializer` will not work for `lambda`s
defined in the module
{{{
Error during serializing test_one.models.<lambda>: ...
}}}
or for `lambda`s imported from other modules:
{{{
ValueError: Error during serializing test_one.utils.<lambda>: ...
}}}
instead of `ValueError: Error during serializing
test_one.models.Model1.field1`.
--
Ticket URL: <https://code.djangoproject.com/ticket/25370#comment:13>
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/071.2122cb6a7f3778ba56da5a0d0a37f54e%40djangoproject.com.
