[Django] #26769: Expose verbosity level in migrations

9 views
Skip to first unread message

Django

unread,
Jun 16, 2016, 1:43:41 PM6/16/16
to django-...@googlegroups.com
#26769: Expose verbosity level in migrations
-----------------------------+--------------------
Reporter: va-andrew | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
It would be especially helpful with data migrations if one could print
status/progress information depending on the "verbosity" option specified
with the management command. The management command already prints to
console, so this would let custom migration operations do the same thing.
For some data migrations, it's useful to log custom status information,
but you don't always want this displayed every time (e.g. when setting up
a test database).

Perhaps verbosity-level could be passed to RunPython callbacks as an
optional argument? Or perhaps the Migration object could expose some sort
of logging functionality?

--
Ticket URL: <https://code.djangoproject.com/ticket/26769>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jun 16, 2016, 2:51:53 PM6/16/16
to django-...@googlegroups.com
#26769: Expose verbosity level in migrations
-----------------------------+------------------------------------

Reporter: va-andrew | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by timgraham):

* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted


Comment:

I guess we could give this a try though passing verbosity all the way from
the management command to the migration operations may be a bit ugly.

--
Ticket URL: <https://code.djangoproject.com/ticket/26769#comment:1>

Django

unread,
Nov 11, 2021, 9:15:54 AM11/11/21
to django-...@googlegroups.com
#26769: Expose verbosity level in migrations
-----------------------------+---------------------------------------
Reporter: Andrew | Owner: Jacob Walls
Type: New feature | Status: assigned
Component: Migrations | Version: 1.9

Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-----------------------------+---------------------------------------
Changes (by Jacob Walls):

* owner: nobody => Jacob Walls
* status: new => assigned


--
Ticket URL: <https://code.djangoproject.com/ticket/26769#comment:2>

Django

unread,
Dec 18, 2021, 5:49:39 PM12/18/21
to django-...@googlegroups.com
#26769: Expose verbosity level in migrations
-----------------------------+------------------------------------
Reporter: Andrew | Owner: (none)

Type: New feature | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by Jacob Walls):

* owner: Jacob Walls => (none)
* status: assigned => new


--
Ticket URL: <https://code.djangoproject.com/ticket/26769#comment:3>

Reply all
Reply to author
Forward
0 new messages