This is especially true when migrations are (accidentally) created for 3rd
party apps, somewhere in your Python path (where the file might be harder
to find).
I can see that this might become quite wide, so maybe it could be
displayed relative to the current working directory then by default, but
uses the absolute path with verbosity >= 1.
--
Ticket URL: <https://code.djangoproject.com/ticket/25063>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* version: 1.8 => master
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/25063#comment:1>
* status: new => assigned
* owner: nobody => nielsvanoch
--
Ticket URL: <https://code.djangoproject.com/ticket/25063#comment:2>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/25063#comment:3>
* Attachment "output_path_to_migration.diff" added.
* needs_tests: 0 => 1
Comment:
[https://github.com/django/django/pull/5582 PR] needs tests. (By the way,
there is no need to attach a patch in Trac and send a PR.)
--
Ticket URL: <https://code.djangoproject.com/ticket/25063#comment:4>
* needs_tests: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/25063#comment:5>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"99a1265a394cb50f5b5aa9046f7b6cd230bc25cf" 99a1265a]:
{{{
#!CommitTicketReference repository=""
revision="99a1265a394cb50f5b5aa9046f7b6cd230bc25cf"
Fixed #25063 -- Added path to makemigration's output of migration file.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25063#comment:6>