#33019: makemigrations produces invalid import path in migration file
--------------------------------+--------------------------------------
Reporter: Choong Jun Jin | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: makemigrations | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
You'll need to [https://docs.djangoproject.com/en/3.2/topics/migrations
/#custom-serializers register a custom serializer] that knows how to
handle your nested field. (A nice example is
[https://github.com/django/django/blob/6c3525a09db5177bf4e3856de85bf8b1300402d5/django/db/migrations/serializer.py#L62-L70
`DatetimeDatetimeSerializer` which adjusts to the `tzinfo` to
`django.utils.timezone.utc`, rather than the underlying implmentation].)
--
Ticket URL: <https://code.djangoproject.com/ticket/33019#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.3bebc0e36bbd97d95a41c4a153a50288%40djangoproject.com.
