[Twisted-Python] Phasing out old-style classes
Steve Steiner (listsin)
listsin at integrateddevcorp.com
Tue Oct 27 10:32:56 EDT 2009
On Oct 27, 2009, at 8:17 AM, exarkun at twistedmatrix.com wrote:
>> At that point there will be two sets of users, the 3.x's that
>> use only new-style classes and the 2.x's for which Twisted classes
>> may be either old or new. It would probably be better to have
>> switched to new-style before then and only have to support the use
>> of new style classes.
> But, presuming this :) I don't think we need to have switched to new-
> style classes for support this scenario. We only have to have written
> all our code such that it continues to work even when there are no
> longer any classic classes. I think that the majority of code in
> Twisted already works even if you flip the new-style switch. We just
> need to identify and fix the few places that don't.
Is this something that can be handled by just running the tests with
the right switch so we can see everything that passes without the
switch but doesn't with?
Is there a "new-style" switch or just -3?
More information about the Twisted-Python