On Thu, 2014-09-11 at 06:33 +0800, Russell Keith-Magee wrote:
> My only concern about pushing the DEP and formally numbering it is
> that we haven't fully worked out what our DEP process *is* yet. I'm
> still recovering from DjangoCon US jet lag, but once that has worn
> off, I've got some ideas
Hi Anssi,
My only concern about pushing the DEP and formally numbering it is that we
haven't fully worked out what our DEP process *is* yet. I'm still
recovering from DjangoCon US jet lag, but once that has worn off, I've got
some ideas about how we can use the DEP process and the technical board
I plan to push the DEP as draft to the django/deps repository. The DEP
will be DEP number 2.
DEP 2 will need to be accepted or rejected eventually. Before that it
doesn't have any official status.
I am planning to do the push as this way it is easier to work on it
collaboratively. There is a lot
I have written a DEP about planned ORM expressions API changes. See
https://github.com/django/deps/pull/5 for the proposed DEP.
The plan is to throw away sql.expressions.SQLEvaluator, rewrite how
expressions work and make aggregates subclasses of expressions.
Short summary of the goals and
