Hello,
I haven’t written to this mailing-list for three weeks because nothing
warranted your immediate attention.
Now the code is in reasonably good shape. Feel free to have a look:
https://github.com/aaugustin/django/commits/multiple-template-engines
I plan to merge this branch within a few da
The team has uploaded a new policy for django-releasers which should enable
more members of the team to roll a release. I’m optimistic we’ll finally be
able to get the 1.7.2 bug fix release out next week.
https://www.djangoproject.com/m/pgp/django-releasers.txt
Besides the work below, I also
As we approach the date for 1.8 alpha, I plan to send a weekly update on
the status of release blocking issues.
We currently have 3 release blockers affecting master. You can use this
Trac filter to see them:
https://code.djangoproject.com/query?status=assigned&status=new&version=master&severity
There's django-admin test --keepdb for this purpose (in Django 1.8).
--
Aymeric.
> Le 20 déc. 2014 à 18:41, Bernard Sumption a écrit :
>
> A proposition: the problem isn't that migrations take 80 seconds, it's that
> this 80 seconds is repeated every time a developer runs tests. How about
>
I did some research, and I can hit the logic in question,
if app_label == settings.AUTH_USER_MODEL and ignore_swappable:
continue
... on both master and with Claude's patch if I follow the steps in this
comment: https://code.djangoproject.com/ticket/22563#comment:8
Andrew, first you added an
A proposition: the problem isn't that migrations take 80 seconds, it's that
this 80 seconds is repeated every time a developer runs tests. How about
serialising the structure and content of the database to disk after
applying migrations, then whenever you need a migrated test database, load
it from
Clause, I believe that line is to allow people to run makemigrations when
AUTH_USER_MODEL points to an app that doesn't yet have migrations; before,
it would fail hard, as the AUTH_USER_MODEL was not in the migrate state and
so nothing could use it, and you couldn't run makemigrations to create it
On Friday, December 19, 2014 6:30:32 PM UTC+1, Tim Graham wrote:
>
> Yes. Claude has worked on the deprecation in
> https://github.com/django/django/pull/3220 but it requires adding more
> migrations to our test suite and he noted that each migration we add to
> Django's test suite adds up to ~3
