#21477: Rename pre/post_migrate argument db to using
--------------------------------------+------------------------------------
Reporter: akaariai | Owner: syphar
Type: Cleanup/optimization | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by andrewgodwin):
I like this approach - we get a DeprecationWarning for the old signals out
of it too, which is a bonus.
I vote +1 on moving DeprecatedSignal somewhere more general (deprecation
is probably good, or possibly django.dispatch). Docs look good apart from
one small typo that I noted on the PR.
Fix those and make the PR mergeable and I'll pull it in.
--
Ticket URL: <https://code.djangoproject.com/ticket/21477#comment:10>
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/066.568e523f594c318a0c32da62d489fe75%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
