Flask-Genshi: Request for comments
- From:
- Dag Odenhall
- Date:
- 2010-07-27 @ 04:00
Hoy, Flaskers.
I'd like some API thoughts for future Flask-Genshi releases.
First off, I was thinking I should add support for rendering from
strings[1], like Flask supports for Jinja. If there are no major
objections I'm going with the bottom proposal there; I feel a little bad
because that's inconsistent with Flask though. On the other hand Flask
does **context but I went with just context because I have optional
keyword arguments; so I can easily add more where Flask can't.
I also don't like select_method being a public module function. It just
complicates the public API and might confuse some users. I want to
_private it and maybe move it to the Genshi class... Should I do a
deprecation period here?
Mainly from Armin, I'd like some comments on signals[2].
Genshi is known to be slow but Chameleon[3] supposedly speeds it up a
great lot. Should I add support for Chameleon in Flask-Genshi? Someone
in #pocoo suggested it should be a separate Flask-Chameleon extension,
but I'm not sure either way.
And for my ego I'm wondering if anyone is actually using
Flask-Genshi? :)
[1] http://bitbucket.org/dag/flask-genshi/issue/2/render-from-strings
[2] http://bitbucket.org/dag/flask-genshi/issue/1/signal-support
[3] http://chameleon.repoze.org/