#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
--------------------------------------+------------------------------------
Changes (by syphar):
* has_patch: 0 => 1
Comment:
I've tried to put the work by loic84 and me together. Result is this here:
https://github.com/django/django/pull/1983
I also added tests for the DeprecationWarning
I'm not entirely sure if
- the documentation should be done differently (no experience here on my
side)
- the DeprecatedSignal is a thing we will need more often and if we should
make it more general and put into
https://github.com/django/django/blob/master/django/utils/deprecation.py
Any thoughts on this?
--
Ticket URL: <https://code.djangoproject.com/ticket/21477#comment:9>
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.e3be45561a7d562e1ccaac8bfe6e0480%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
