Right now one of my code-bases is filled with assertions like:
with raises(SpecificError) as error:
some_action()
assert 'specific message' == str(error)
Why not change `raises` to allow instances of exceptions as well:
with raises(SpecificError('specific message')):
some_action()
I thi
Hi Holgen,
On Sat, Oct 12, 2013 at 10:12 AM, holger krekel wrote:
> My comments and wishes (others may comment as well!):
>
> - i'd collapse NAME and VERSION columns to save space, i.e.
> "pytest-bdd-0.6.1".
>
> - what about adding download numbers?
>
> - as to code organisation: you can leav
On Mon, Oct 14, 2013 at 14:21 -0300, Bruno Oliveira wrote:
> Hi Holgen,
hi Brunon! :)
>
> On Sat, Oct 12, 2013 at 10:12 AM, holger krekel wrote:
>
> > My comments and wishes (others may comment as well!):
> >
> > - i'd collapse NAME and VERSION columns to save space, i.e.
> > "pytest-bdd-0.6
On Mon, Oct 14, 2013 at 17:19 +0200, Vladimir Keleshev wrote:
> Right now one of my code-bases is filled with assertions like:
>
> with raises(SpecificError) as error:
> some_action()
> assert 'specific message' == str(error)
>
> Why not change `raises` to allow instances of exceptions as wel
An alternative would be to use another "raises" function, like
with raises_message(SpecificError, 'specific message'):
some_action()
One problem is bloating the API a little more...
Cheers,
Bruno.
On Mon, Oct 14, 2013 at 5:50 PM, holger krekel wrote:
> On Mon, Oct 14, 2013 at 17:19 +0200
Hi Holger,
On Mon, Oct 14, 2013 at 5:32 PM, holger krekel wrote:
> On Mon, Oct 14, 2013 at 14:21 -0300, Bruno Oliveira wrote:
> > Hi Holgen,
>
> hi Brunon! :)
>
Hehehe, oops.
>
> > On Sat, Oct 12, 2013 at 10:12 AM, holger krekel
> wrote:
> > >
> > > - i'd collapse NAME and VERSION columns to
