Universal Jinja: a crazy idea for a Python-ready front end

Re:Universal Jinja: a crazy idea for a Python-ready front end by jjawssd on Saturday July 15, 2017 @01:47PM (#14777896)

I'd like to hear more about:

  - the broken mix of pythonisms
  - the arbitrary-feeling restrictions
  - the oddly missing pieces

Because I can't find any.

[ Parent | on HN ]

Re:Universal Jinja: a crazy idea for a Python-ready front end by nrser on Saturday July 15, 2017 @02:06PM (#14778016)

Check this fiasco out for starters:

https://github.com/pallets/jinja/issues/659

> It was never documented that you can override variables from higher scopes

But you could, and people did... because that's what people do: they try stuff that seems reasonable and if it works they use it. And then someone "fixed" it in a minor release and things started breaking. BTW the error message is

    KeyError: 'undefined variable: 0'

Fun way to spend an afternoon, I can assure you.

I used Jinja2 happily for years on a web app, but that thing pretty much just styled a page for flash to sit in and drew some forms and menus. I use it now via Ansible and have come to despise it through and through.

[ Parent | on HN ]

Re:Universal Jinja: a crazy idea for a Python-ready front end by FatalBaboon on Saturday July 15, 2017 @02:46PM (#14778220)

The other day I was debugging an Ops issue only to find that it originated in a python-based executable. I soon found out it was a feature unfinished and buggy. There is a github issue that documents it, it has been around for no less than 10 years. 5 people offered PRs that got rejected for style and they are still discussing how to fix the bug in the most pythonist way.

I'll try to find it again. I obviously ditched the

[ Parent | on HN ]

Re:Universal Jinja: a crazy idea for a Python-ready front end by jjawssd on Saturday July 15, 2017 @11:29PM (#14780326)

Fastest solution: fork the code and merge the PRs into your own branch yourself.

[ Parent | on HN ]