On 2011-03-13 15:58:20 -0400, Mike Orr said:
On Sun, Mar 13, 2011 at 11:08 AM, Alice Bevan–McGregor
<al...@gothcandy.com> wrote:
* marrow.wsgi.objects (WebOb) request/response/exceptions
These are fully WebOb compatible? WebOb has become essentially the only
multi-framework Request/Response, so I dont' want to interfere with it
becoming a standard. It's easier to program in WebOb than raw WSGI.
No, it is not directly WebOb compatible, though conversion shouldn't be
too difficult. Right now m.w.objects contains a complete templatable
exception collection (care of Alex Grönholm) and enough of the
request/responses to get working, if simplified data in and out. (The
examples using Response objects, @wsgify decorator, etc. are all
functional.)
I aim to correct some perceived (by me) flaws in the API; things like
multiple body accessor methods (how many people honestly assign a file
then read back the unicode?), etc.
- Remove formal dependencies on Chameleon, Mako, and PasteDeploy in
Pyramid. Some of these are more properly dependencies of the specific
applications which are using them.
There exists a package called alacarte which offers a back-end agnostic
templating interface. It already supports Mako, Jinja2, and a handful of
others, including serialization formats like JSON, Bencode, and YAML. It
was built to replace the ancient (and crufty) TurboGears 1 "buffet" API.
Does it require an entry point for each templage engine as Buffet does?
That's what we ultimately removed from Pylons because it was a level of
indirection and complexity that wasn't really necessary.
It is if you want the onus on supporting frameworks to be on the
template engine author and not on the over-worked framework developers.
;) The Buffet API was terrible, the alacarte API is extremely simple,
and you can even register template engines imperatively.
— Alice.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
