#22788: Custom migration operations are rewritten incorrectly
----------------------------+------------------------------------
Reporter: schinckel | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by schinckel):
Better patch does contain tests, but I couldn't come up with a way to make
the test fail when two classes have the same name, but a different path.
I needed to import the class using `from ... import ...` syntax, as
otherwise there were issues related to namespacing and the term
migrations, which I may try to work out.
--
Ticket URL: <https://code.djangoproject.com/ticket/22788#comment:4>
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/067.b62dbb2b1862a06da565be4da860f3e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
