If we went with a separate command, would there be any problem having 
--list on both migrate and showmigrations. I feel like deprecating it off 
of migrate will cause more complaints about needless deprecations.

On Wednesday, October 29, 2014 9:28:51 PM UTC-4, Andrew Godwin wrote:
>
> This used to be called "graphmigrations" in South, so I'm +0 on moving it 
> to showmigrations; I don't want migrate to gain any extra functionality. 
> That said, I tried moving --list to something separate during the 1.7 phase 
> but there were objections to people who liked it on migrate.
>
> I don't really mind which way you go, to be honest; both seem like 
> sensible places. Other people might have stronger opinions.
>
> Andrew
>
> On Wed, Oct 29, 2014 at 4:44 PM, Markus Holtermann <
> [email protected] <javascript:>> wrote:
>
>> Hey folks,
>>
>> A few weeks ago I opened a ticket (
>> https://code.djangoproject.com/ticket/23359) to add the ability to show 
>> a migration plan similar as listing all migrations within a project 
>> (manage.py migrate --list). After some discussions on IRC and on the first 
>> pull request (https://github.com/django/django/pull/3116) we realized 
>> that there might even be more use cases, e.g. to output all migration files 
>> as a dot file to generate a graph (
>> https://github.com/django/django/pull/3116#issuecomment-53565075). 
>> That's when I opened a second pull request that moves the existing "--list" 
>> and the new "--plan" option from the "migrate" command to a 
>> "showmigrations" command.
>>
>> Any suggestions on which way I should follow, integrate in "manage.py 
>> migrate" (pull request 3116: https://github.com/django/django/pull/3116) 
>> or add a new dedicated command "manage.py showmigrations" (pull request 
>> 3153: https://github.com/django/django/pull/3153)?
>>
>> /Markus
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/f8bdabfc-f005-4e8e-b1d9-0b69dfdedd82%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-developers/f8bdabfc-f005-4e8e-b1d9-0b69dfdedd82%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d629e9c9-5ea1-46a4-b410-ceec6aeddfa7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to