#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: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by syphar):
Just a thought, then why did Andrew keep not used arguments and built the
new signals as alias to the old ones?
- see this
(https://github.com/django/django/commit/68e0a169c4f9fa7f8071e014b274fd59e970f9a3),
- deprecation here
https://github.com/django/django/blame/master/docs/internals/deprecation.txt#L167
It seems like the two kwargs `create_models` and `created_models` are only
kept to stay backwards compatible.
Or am I wrong and these arguments _are_ still important, even if you use
migrations? (so, not comparable to this ticket).
Thanks for looking into this.
--
Ticket URL: <https://code.djangoproject.com/ticket/21477#comment:5>
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.6534ee5d0ca9a42e2afa5465545dcd0f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
