On Aug 21, 1:53 pm, Peter Otten <[EMAIL PROTECTED]> wrote:
> Silfheed wrote:
> > On Aug 21, 1:32 am, James Stroud <[EMAIL PROTECTED]> wrote:
> >> Silfheed wrote:
> >> > Heyas
>
> >> > So this probably highlights my lack of understanding of how naming
> >> > works in python, but I'm currently using
Silfheed wrote:
> On Aug 21, 1:32 am, James Stroud <[EMAIL PROTECTED]> wrote:
>> Silfheed wrote:
>> > Heyas
>>
>> > So this probably highlights my lack of understanding of how naming
>> > works in python, but I'm currently using FailUnlessRaises in a unit
>> > test and raising exceptions with a st
On Aug 21, 1:32 am, James Stroud <[EMAIL PROTECTED]> wrote:
> Silfheed wrote:
> > Heyas
>
> > So this probably highlights my lack of understanding of how naming
> > works in python, but I'm currently using FailUnlessRaises in a unit
> > test and raising exceptions with a string exception. It's wor
Silfheed wrote:
> Heyas
>
> So this probably highlights my lack of understanding of how naming
> works in python, but I'm currently using FailUnlessRaises in a unit
> test and raising exceptions with a string exception. It's working
> pretty well, except that I get the deprecation warning that ra
Heyas
So this probably highlights my lack of understanding of how naming
works in python, but I'm currently using FailUnlessRaises in a unit
test and raising exceptions with a string exception. It's working
pretty well, except that I get the deprecation warning that raising a
string exception is
