I've been ignoring the fact that WebOb has very light test coverage for
a while now, but I've just run into a bug that makes it clear that my
blissful head-in-the-sand days are nearing an end.
Is anyone interested in leading a task to give WebOb 100% test coverage?
It's a fairly large task, inglor
On Wed, 2010-12-29 at 15:42 -0800, Mike Orr wrote:
> On Wed, Dec 29, 2010 at 1:28 PM, Marius Gedminas wrote:
> > On Wed, Dec 29, 2010 at 10:56:29AM -0800, Seth wrote:
> > The docs say that messages don't have to be strings, so you can do
> > exactly that, if you push dicts like this:
> >
> > requ
On Wed, Dec 29, 2010 at 1:28 PM, Marius Gedminas wrote:
> On Wed, Dec 29, 2010 at 10:56:29AM -0800, Seth wrote:
> The docs say that messages don't have to be strings, so you can do
> exactly that, if you push dicts like this:
>
> Â request.session.flash(dict(message='Hello!', queue='welcome')).
>
>
On Wed, Dec 29, 2010 at 10:56:29AM -0800, Seth wrote:
> With regards to the flash messaging API, is there a reason why you chose not
> to provide a method which returns *any* flash message from any queue
> (preferably with a msg:queue key:val)? It would sure make template code
> easier if I *do*
Hey Chris,
With regards to the flash messaging API, is there a reason why you chose not
to provide a method which returns *any* flash message from any queue
(preferably with a msg:queue key:val)? It would sure make template code
easier if I *do* want different queues but *don't* really need the
