Tim Perevezentsev

Preprocessing and postprocessing

2

I propose preprocessing and postprocessing during template parsing. Preprocessing syntax: ``` @tag:pre @tag:pre,pre1 ``` Postprocessing syntax: ``` @tag::post @tag::post,post1 ``` Mixed: ``` @tag:pre:post ``` Note: I'm not sure about multiple...

Solution for @pre @code content

1

There are cases, when text content is needed "as is" (with special indention). I think that we need to introduce two more tokens for this case. Begin mark of such...

Get rid of global vars used in comprehensions.

It's easy to implement and is so useful.

Each node, if it has no conditional attributes `@.attr(value)` or `@+attr(value)` can be represented as strings concatenation.

Now if an exception is raised in slot of inherited template there is no sane way to know the actual place (line number, source code). That's sad. So I propose...

I think we need to parse python expressions by our self. This way we can limit subset of valid expressions in context of mint syntax.

In `utils`. So that people can make markup with generated text without project server code.

Update pygments support. It is trailed behind now.

Need idea for syntax of such things.