On Fri, Feb 15, 2013 at 10:52 AM, Volker Braun <vbraun.n...@gmail.com> wrote: > On Friday, February 15, 2013 6:15:06 PM UTC, Robert Bradshaw wrote: >> >> > Since I'm currently working myself through groups to get them off the >> > old >> > parent, I had some success with the following approach: Split the parent >> > (say, Ring) into and old and a new parent. They can both be called Ring >> > as >> > long as they live in different files. Then gradually transition >> > individual >> > rings from the old to the new parent Ring. That lets you break up the >> > task >> > into manageable bits. Otherwise its just impossible for a single person >> > to >> > rewire all rings in one go. >> >> That could make sense, as long as we're *never* checking that anything >> is an instance of Ring. > > > Or, more likely, replace all occurrences of isinstance(foobar, Ring) with > is_Ring() and make is_Ring() answer true for the old and the new Ring.
We'd need to do the same for Field, etc. as well. This is why I went with leaving the old parents in the class hierarchy and manually disallowing their use. - Robert -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
