On Thu, Dec 2, 2010 at 6:23 AM, Terry Reedy <tjre...@udel.edu> wrote: > It would be easiest to just remove the two lines above. > Or should I define functions _xxx names that issue a deprecation warning and > attach them as attributes to each object? (Defining instance methods would > not be the same).
Given that functions are converted to bound methods only on retrieval from an instance, why wouldn't it be the same? But yes, if you want to get rid of them, then deprecation for 3.2 and removal in 3.3 is the way to go. Alternatively, not deprecating them at all and just leaving them undocumented with a comment in the source to say they have been deliberately omitted from the docs would also be fine. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
