On Mar 14, 2011, at 4:13 PM, Stephen Lacy wrote:
Yeah, implicitly breaking HEAD sucks. :)
Using the request_method to explicitly only handle a single request method with
a single view isn't implicit. One explicitly has to set that predicate. As
using a custom predicate for a limited set of
On Mar 10, 2011, at 1:44 PM, Stephen Lacy wrote:
What's the recommended way to get proper HEAD request support using pyramid +
mod_wsgi?
Right now, with my vanilla mod_wsgi configs, and request_method='GET' on my
view_config decorators, my HEAD requests are 404'ing. I tried setting
On Mar 10, 2011, at 1:44 PM, Stephen Lacy wrote:
What's the recommended way to get proper HEAD request support using pyramid +
mod_wsgi?
Right now, with my vanilla mod_wsgi configs, and request_method='GET' on my
view_config decorators, my HEAD requests are 404'ing. I tried setting
On Mar 10, 2011, at 2:17 PM, Stephen Lacy wrote:
Ah, the custom predicates makes sense, but the syntax is really obtuse.
I'll look (briefly) at coding up request_method=('GET', 'HEAD') and submit a
pull request if there's no objection here. I suspect it's as simple as
replacing == with
On Mar 9, 2011, at 5:00 AM, ZHUO Qiang wrote:
Hi,
Since I find the old pylons's way of RESTful HTTP _method tunnel very
handy, I have the following customize predicts to emulate the same effects in
Pyramid:
# this predicts will using the both real HTTP method and _method for
On Mar 4, 2011, at 12:39 PM, Chris McDonough wrote:
On Fri, 2011-03-04 at 04:43 -0800, Andrey Petrov wrote:
Re: Excessive dependencies.
Of these, the only ones to very easily *not* install would be Mako,
Chameleon, PasteScript, Paste, and PasteDeploy. The others are core
dependencies
On Mar 4, 2011, at 3:42 PM, Blaise Laflamme wrote:
That said we definitely need to communicate the right message, provide
the right level of documentation for the targeted audience, have a
better way to expose tools and contributions, etc...
Who is the targeted audience? Currently it seems
