[Twisted-Python] Depreciation of trial.unittest functions?
James Y Knight
foom at fuhm.net
Sat Dec 31 23:29:12 EST 2005
On Dec 31, 2005, at 5:16 AM, Jonathan Lange wrote:
> On 12/30/05, Paul Swartz <paulswartz at gmail.com> wrote:
>> I'm not sure if Conch is the only project that did this, but it
>> used the
>> trial.unittest.* functions instead of methods on TestCases. I
>> used them
>> to avoid having to pass TestCase instances around all over the
>> or using a global variable. To avoid the depreciation warnings, I've
>> starting using the unittest._inst global variable, but I doubt
>> that this
>> is the appropriate way to change my code. Is this just not a
>> way of using Trial, or is there something else I should be doing?
> This is just not a supported way of using Trial.
Given that the methods don't use self at all (and at least I can't
forsee any need to in the future), is there a reason they can't be
class methods, so that unittest.TestCase.assertEquals(a, b) would work?
More information about the Twisted-Python