Creating in-memory migrations for all apps that don't have migration
files seems to be an option to solve the dependency problem. This would
even allow apps without migrations to depend on those with migrations.
We have to consider though, that there are tens of apps and hundreds of
models in our
My main argument for removing them entirely was the dependency issues
between apps with and without migrations. Having syncdb use SchemaEditor is
a big step and one I'm happy we've got to, but the only advantage of
keeping syncdb is for the test suite and I'd rather we approach that more
as "migrat
Hello,
I published my update for week 15:
https://myks.org/en/multiple-template-engines-for-django/#2015-01-18
--
Aymeric.
> On 11 janv. 2015, at 00:02, Aymeric Augustin
> wrote:
>
> Hello,
>
> Here’s episode 14:
> https://myks.org/en/multiple-template-engines-for-django/#2015-01-11
>
>
Tim recently did a fabulous job of removing deprecated code for the
future 1.9 on master. Thanks for that.
However, one thing he removed was support for apps without migrations.
https://github.com/django/django/commit/7e8cf74dc74539f40f4cea53c1e8bba82791fcb6
Considering that we have to keep inter
Hi Preston,
On 14 janv. 2015, at 20:43, Preston Timmons wrote:
> As a quick recap:
>
> First, this branch uses origins everywhere: for extends history, for
> TemplateDoesNotExist errors, etc. There's no more 4-tuple of statuses.
Good.
> Second, I use these attributes on the origin:
>
> engin
