#22725 closed Bug (fixed)
Migration.run_before does nothing
Reported by: | Chris Beaven | Owned by: | |
---|---|---|---|
Component: | Migrations | Version: | dev |
Severity: | Release blocker | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The attribute is there, and the comment shows how it should work (which is exactly what I need).
The code to make it work was non-existant.
Pull request below...
Change History (6)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Owner: | set to |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:5 by , 10 years ago
Yeah, I haven't figured out how to backport merges easily yet without just cherry-picking the changes.
comment:6 by , 10 years ago
I think that cherry-picking is fine, just edit the commit message so that it includes the ticket number.
Note:
See TracTickets
for help on using tickets.
https://github.com/django/django/pull/2736