'return' makes sense because views return a response. Whether the response
has an error code of 200, 301 or 5xx is a separate concern. Of course
exceptions make sense too.
In Pyramid you could replace the standard context finding methods with a
view that raises exceptions and build your whole a
On 26/05/2011 14:15, Daniel Holth wrote:
In Pyramid you could replace the standard context finding methods with a
view that raises exceptions and build your whole application out of
exception views.
...which result in the PSU (That's *not* the Pyramid Secret Underground,
which doesn't exist an
On Thu, May 26, 2011 at 6:15 AM, Daniel Holth wrote:
> 'return' makes sense because views return a response. Whether the response
> has an error code of 200, 301 or 5xx is a separate concern. Of course
> exceptions make sense too.
This only became an issue because HTTPException happens to be a WS
On Tue, 2011-05-24 at 18:22 -0700, Jerry wrote:
> Thanks Mike.
>
> Chris, so how about this to offload some work from the template/helper
> --
>
> if v is not None:
> v = quote_plus(str(v))
> result += '%s%s=%s' % (prefix, k, v)
That's probably fine. It will need tests and d
Howdy!
On 2011-05-25 14:50:58 -0700, Mike Orr said:
Alice, thank you for correcting any misconceptions about Marrow, and
for documenting it on the Brainstorm page for future reference. I
apologize if I've made any mischaracterizations, either from reading
something that was false or interpret
On Thu, May 26, 2011 at 3:39 PM, Alice Bevan–McGregor
wrote:
>> Argparse does what it does reasonably well; I have not yet gotten sick
>> enough of it to jettison it.
>
> For sure there is no point taking an existing working solution and throwing
> it to the wind to re-engineer it under a differen
Howdy!
On 2011-05-26 16:11:45 -0700, Mike Orr said:
On the other hand, those who are already using Argparse may find Marrow
unnecessary...
There are always alternate parsers and the option to do it by hand.
Also, please ensure you mention a specific Marrow package rather than
the entire su
On Thu, May 26, 2011 at 3:39 PM, Alice Bevan–McGregor
wrote:
> Unfortunately, the majority of the Marrow projects that could
> benefit Pyramid would require core changes, thus a fork and a number of
> branches to explore the options, not just add-on packages or adaptive
> HOWTOs.
In that case, wh
