id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,branch,branch_author,launchpad_bug
6076,add an automated test which will fail if any old-style classes (AKA classic classes) are added,glyph,,"We have some classic classes in Twisted, but we don't want to add any more. (Citation needed: where's our policy document that says no classic classes? I can't find it.) Python 3 is new-style only and it would be nice if we only had one kind of object model; however, application code may well be relying upon the classic-class behavior of its inherited classes and fail in an ugly way (""Cannot create a consistent method resolution order"" being the most popular one).

This is an easy thing to miss in a review; it's just the ''absence'' of the word ""object"".  It could easily be enforced automatically, and it should be.

(This would be part of the trial test suite but it's not a ""unit test"" really, so let's not call it that.)",task,new,normal,,core,,,ashwini.oruganti@…,,,