From: SourceForge.net <no...@so...> - 2006-12-10 06:47:51
|
Bugs item #1605011, was opened at 2006-11-29 00:08 Message generated for change (Comment added) made by cgroves You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1605011&group_id=12867 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: targeted for 2.2beta1 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Charles Groves (cgroves) Assigned to: Charles Groves (cgroves) Summary: setting __bases__ on a class doesn't change its instances Initial Comment: Setting __bases__ on a class doesn't cause methods from the new bases to show up in its instances. This causes test_mutable_bases_catch_mro_conflict and test_mutable_bases in test_descr.py to fail. ---------------------------------------------------------------------- >Comment By: Charles Groves (cgroves) Date: 2006-12-10 01:47 Message: Logged In: YES user_id=1174327 Originator: YES Added in r3019. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1605011&group_id=12867 |