On Montag, 5. August 2013 19:43:16 Michael Merickel wrote:
> actually
> https://github.com/Pylons/pyramid_handlers/issues
Thanks, did that now.
Unfortunately, I'm completely overcharged ATM, hence sorry for not providing a
patch/pull req..
Cheers,
Pete
> On Mon, Aug 5, 2013 at 7:19 PM, Steve P
actually
https://github.com/Pylons/pyramid_handlers/issues
On Mon, Aug 5, 2013 at 7:19 PM, Steve Piercy wrote:
> On 8/5/13 at 11:57 PM, h...@urpla.net (Hans-Peter Jansen) pronounced:
>
> > Dear Chris,
> >
> > don't know your favorite way to be informed about such issues:
>
> https://github.com/P
On 8/5/13 at 11:57 PM, h...@urpla.net (Hans-Peter Jansen) pronounced:
> Dear Chris,
>
> don't know your favorite way to be informed about such issues:
https://github.com/Pylons/pyramid/issues
Ideally with a pull request that fixes it. :D
Next favored would be here or in IRC.
--steve
> FYI,
Dear Chris,
don't know your favorite way to be informed about such issues:
FYI, building on top of a fairly current pyramid stack, two tests of
pyramid_handlers fail:
[7s] + python setup.py nosetests --with-coverage
[7s] running nosetests
[7s] running egg_info
[7s] writing requi
