On 4/5/19 8:16 PM, Adam Johnson wrote:
FYI Jinja2 allows (most) python expressions, so this would Just Work(TM):
{{ myvar.startswith("x") }}
Django Template Language has a lot of legacy that prevents this from
happening, afaiu it would not be possible to move to it.
For "legacy" read "philo
I have updated my proposal please have a look
On Wednesday, April 3, 2019 at 9:22:57 PM UTC+5:30, Carlton Gibson wrote:
>
> Yes, just pseudo code — so when reviewing your proposal next week it's
> easy to see that it'll be the right approach. 🙂
>
> On Wednesday, 3 April 2019 17:51:18 UTC+2, PARTH
Agreed. I will document that 1.11 and 2.1 require psycopg2 *2.5.4* through
*2.7.7* versions.
We can re-open this discussion in the future if e.g. psycopg2 2.8.x will
contain some important security patch.
--
You received this message because you are subscribed to the Google Groups
"Django dev
OK, so for me, this should go into v2.2, but not v2.1 or v1.11. (I see you
already backported to 2.2 so... 🙂)
My general take here is that we could be half-a-notch more generous
backporting to the current version (e.g. 2.2 now) but should be just as
strict as we are once a version is out of mai
FYI Jinja2 allows (most) python expressions, so this would Just Work(TM):
{{ myvar.startswith("x") }}
Django Template Language has a lot of legacy that prevents this from
happening, afaiu it would not be possible to move to it.
It's not hard to move your templates (asides from those extending e
