https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215651
Vladimir Krstulja <vlad-f...@acheronmedia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |security
--- Comment #6 from Vladimir Krstulja <vlad-f...@acheronmedia.com> ---
(In reply to Olivier Duchateau from comment #5)
Ok. Let me just add this too, it appears that the asyncsupport.py is imported
only if there's async support (environment.is_async == True), there's a
conditional import for the template in compiler.py. I just ran a quick and
dirty test in a py27 virtualenv, and Jinja2 2.9.3 imports fine. I have to test
it with actual templates used, but I don't think there's a need to hard-limit
Jinja2 to python2.7 only.
Please correct me if I'm wrong.
Also please be aware that there are 29 reverse dependencies of py-Jinja2, some
of which, to my knowledge as I haven't tested all of them, build and work fine
at the moment with DEFAULT_VERSIONS= python=3.5, most notably Sphinx and Flask.
And only a handful of py3-Jinja2, I presume for some cases where those rdeps
must be forced to py35-*
So another question is why is py3-Jinja2 an entirely separate port and not a
slave? If a sweeping change like this is to be done, perhaps it should be done
closer to the next Quarterly cut-off, and we can combine the ports and fully
switch to 2.9.x?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
