针对特定用例中 Python Web 开发的最佳模板引擎的建议

发布于 2024-12-06 10:53:48 字数 915 浏览 0 评论 0原文

对于 Python Web 开发，有大量的模板引擎可供选择。我的工作仅限于一组相当狭窄/特定的用例。对这些的描述可能会向那些对其中许多/大多数具有工作知识的人建议，其中一个更适合我的特定用例。换句话说，这组中可能有一个针对接近我自己的用例的规范进行了优化，如果是这样，我想知道它是什么。

以下是描述这些用例的标准：

服务器端语言是python，但我希望我不需要太多我的模板中的 python 表达式
我将把它与 python Web 服务器 CherryPy 一起使用并且（可能） Twisted
jQuery 是数据显示的语言编写库/插件
模板描述用于数据显示的抽象网页 （BI 仪表板，这是一个公平的描述）一旦服务器将数据传送到模板（响应在先行词上提交的表单选择页）我只想在网格中显示数据，例如，jQuery 插件 jqgrid，或在图中，例如，中的标准类型之一 Flot
性能至关重要，但范围非常狭窄——仅适用于数据处理和渲染——我希望网格经常被填充具有数千个数据行（尽管网格本身将是分页）；同样，这些地块很容易有一千个左右数据点，但同样，预处理和计算将是在其他地方完成
很少需要丰富的语法（不需要复杂的多路分支等）--我更喜欢在服务器（同样，数据过滤几乎总是由我用来渲染数据的 jQuery 插件）
同样，用户与显示数据的交互是通过 jQuery 插件提供的本机元素（例如，向上/向下翻页、排序等）
“设计者友好”的模板并不是很重要（不是因为我不喜欢设计师，但因为所需的设计工作应该足够低，以便我什至可以做到。

原文

For Python Web Development, there is a large selection of template engines. My work is limited to a fairly narrow/specific set of use cases. A description of these might suggest to someone who has a working knowledge with many/most of them, that one of them is better suited for my particular use cases. In other words, there might be one among this group that was optimized against a spec close to my own use case, if so i would like to know what it is.

Here are the criteria that describe those uses cases:

server-side language is python, but i hope that i don't need a lot
of python expressions in my templates
i will use it with the python web servers CherryPy and (likely)
Twisted
jQuery is is the language in which the data display
libraries/plug-ins are written
the templates describe abstract web pages used for data display
(BI Dashboard, is a fair description) once the server delivers the data to the
template (in response to form selections submitted on an antecedent
page) i just want to display the data in a grid, e.g., the jQuery
plug-in jqgrid, or in a plot, e.g., one of the standard types in
Flot
performance is critical, but the scope is very narrow--only for a
data handling and rendering--i expect grids will often be populated
with several thousand data rows (though the grid itself will be
paginated); likewise, the plots could easily have a thousand or so
data points, though again, the pre-processing and computation will be
done elsewhere
very little need for a rich syntax (no need for complex multi-way
branching, etc.)--i prefer to do any processiong/computation on the
server (and again, data filtering will almost always be done by the
jQuery plugin i use to render the data)
likewise, the user's interaction with the displayed data is through
native elements supplied by the jQuery plug-in (e.g., page up/down,
sort, etc.)
a "designer-friendly" template is not really important (not because i
don't like designers, but because the design effort required should
be low enough so that i even i can do it.