#28250: migration depending on non-existing legacy migration
-------------------------------+--------------------------------------
Reporter: Brian May | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.10
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 Raphaël Hertzog):
Replying to [comment:7 Marten Kenbeek]:
> You should be able to get the `Migration` object like this:
>
> {{{
> self.graph.nodes[parent]
> }}}
Thanks, I updated my branch and asked the bug submitter to retry with
updated packages.
--
Ticket URL: <https://code.djangoproject.com/ticket/28250#comment:8>
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/063.fe8a04f84cf540614688259e486a64de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
