Hi Aymeric,
Just some quick feedback - I think it's perfectly reasonable not to be
writing any docs or tests at this point. It seems like the nitty-gritty
details are likely to be affecting various API decisions that you have
to make, and there is no point writing either docs or tests when API is
Thanks for pointing out the index improvement DEP Shai, I hadn't seen that
yet.
It's important to note that right now, index names are not re-creatable in
retrospect. They rely on the names of models and fields, that are free to
be renamed. So a complete rethink will be needed if introspection
Hi,
Thanks both for the feedback; I was not seeing the whole issue with JS, and I
now share your concerns.
To me, the ticket can be closed as won't fix
(https://code.djangoproject.com/ticket/23927).
Thanks Tim for raising the issues that brought us here.
Cheers,
Jorge
On Sunday, November 30,
Hello,
Here’s my eight update — this is getting repetitive :-)
https://myks.org/en/multiple-template-engines-for-django/#2014-11-30
--
Aymeric.
> On 23 nov. 2014, at 00:02, Aymeric Augustin
> wrote:
>
> Hello,
>
> I published my seventh update:
> https://myks.org/en/multiple-template-engi
I'm afraid I have to agree the gain does not merit the effort.
To the average user, I think the query string already looks like it's weird
code stuff (with &=?) so I don't think it being in a different language
would improve things that much.
Marc
On 28 Nov 2014 13:36, "Florian Apolloner" wrote:
