Some of you may be wondering how the new coercion model is coming along. After a heroic effort by many people at Dev Days 1, and a little followup work, we managed to merge the coercion branch into 3.0.3 and got all doctests to pass with the exception of /modular and /schemes/generic. It has become apparent however that the "coercion" branch contains much, much more than just coercion. We also want to have the highest assurance of the integrity of the resulting code which is hard to do with such a large set of interdependent changes all lumped together as a single patch bomb. Therefore we have decided to take the work we have so far and move it over piece by piece. Specifically, we are inserting a new Parent underneath the the old Parent object so we can migrate one thing at at time. We will also be merging in the many not-directly related improvements individually as separate tickets. The most significant impact this will have is that it may take longer for the "new coercion" to be 100% done, but the part that is done will be in Sage itself, as well as being sanely refereed.
- Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
