Re: Must a Django Database Support Migrations?

Hi Ivan, I'm not sure what you're asking here - are you asking to have a way to not have Django create the migrations recording table? I was under the impression that it was only created when migrate was run (at least, that was my original intention) so if you're managing your own schema just

Re: Must a Django Database Support Migrations?

>From Andrew: "The only extra thing it would achieve is not having Django record migrations in the django_migrations table" The Django Users thread on how to keep this table from being created seemed to result in the 'solution' being either to stay with 1.6 or comment the relevant lines in the

Re: Settings: lists or tuples?

Hi Andreas, I'm completely in agreement with you that *in theory* using tuples would be a (very marginal) improvement. I also happen think that the idea that tuples are semantically different from simply being immutable lists is a nonsense - regardless of what a particular section of

Re: Settings: lists or tuples?

On 20 janv. 2015, at 18:52, Andreas Kahnert wrote: > But since you all seem to like lists that much, maybe a compromise would be > to explicitly note in the docs that there is a danger in using lists which > can be prevented by tuple usage. As explained in my

Re: Settings: lists or tuples?

Just for completness: accidential assignment to the settings object itself could be easily prevented with a __setattr__ method on its class, since django yields on various other places about configuration problems it could not be wrong if the programmer gets noted about an illegal assignment.

Re: Fellow Report - January 16, 2015

Definitely. I don't think any of the patches I've written have sat without review for longer than a day or two. The turn around on feedback has been amazing. I really hope this program is picked up again. Thanks Tim and Berker. - Josh On Tuesday, 20 January 2015 17:16:39 UTC+11, Anssi