I think its important to distinguish temporarily vs. permanently disabling a doctest. The Sage library has always some ends that are being worked on, and I think its OK to temporarily disable a doctest until the functionality is in place. Essentially, the doctests show what is currently implemented and believed correct. On the other hand, one should only permanently remove a doctest if one also removes the associated code.
In the case at hand, it seems like the OSX issue is under investigation and will be fixed soon. Then why not remove the doctests so we can ship Sage-4.7. We already have trac to keep track of bugs, we don't really need an independent "bugtest" doctest feature. However if we discover that the OSX issue is due to an Apple bug that is outside of our control then there should be a doctest that fails on that particular buggy platform. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
