On Mar 18, 2011, at 9:36 PM, [email protected] wrote: >> In concrete, I say that we should: >> >> - Deprecate those names that are deprecated in Python 3 (I mean, still >> provide the functionality, but with a DeprecationWarning) >> >> - Stop using them in internal code. >> >> - Fix documentation to explain all this and show the chosen methods. >> >> What do you think? > > +1 from me.
Me too, except the order is wrong: >> - Fix documentation... >> - Stop using them... >> - Deprecate those names... In the past we've made an unfortunate habit of deprecating names and emitting tons of warnings without either explaining why they've been deprecated or removing our own usage. Let's get those done first before we start inserting warnings. Thanks! :)
_______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
