Re: sys.exit(1) from makemigrations if no changes found

2014-11-10 Thread Tim Heap
The preference seems to be for option 3, adding a new flag --exit. I have implemented this and updated the pull request at https://github.com/django/django/pull/3441. On Wednesday, October 29, 2014 12:22:42 PM UTC+11, Tim Heap wrote: > > Hi all, > > I have created a ticket for th

Re: sys.exit(1) from makemigrations if no changes found

2014-10-29 Thread Tim Heap
he commands or running a script. > What would the workflow be where you would make migrations but not apply > them? > > D > > > > On 30 October 2014 12:29, Tim Heap > wrote: > > The backwards compatibility issue I was thinking of is for people using > >

Re: sys.exit(1) from makemigrations if no changes found

2014-10-29 Thread Tim Heap
l patch, it should be fine. >>> >>> (As for being surprising compared to grep, there are many other commands >>> with different exit codes one could draw parallels to; I'm not sure being >>> consistent with a very different utility is a worthwhile cause). >>

Re: sys.exit(1) from makemigrations if no changes found

2014-10-29 Thread Tim Heap
th a very different utility is a worthwhile cause). > > Andrew > > On Tue, Oct 28, 2014 at 6:22 PM, Tim Heap > > wrote: > >> Hi all, >> >> I have created a ticket for this ( >> https://code.djangoproject.com/ticket/23728) but I would like some input >

sys.exit(1) from makemigrations if no changes found

2014-10-28 Thread Tim Heap
Hi all, I have created a ticket for this ( https://code.djangoproject.com/ticket/23728) but I would like some input before I work on it. I will copy the content of the ticket below for ease of reading: It would be very useful for continuous deployment, testing, commit hooks, and other applicat