On 5 February 2011 08:17, Mate Kosor <mate.ko...@gmail.com> wrote: > I don't know why the checks don't work for package python, but if I > could make a suggestion maybe it would be better that the check ships > that package because now the check is nonfunctional.
IMHO that would be a bad idea. It's better to be aware of the issue than just to cover up the failures.The actual tests that fail differ from system to system. It should also be noted that a large number of the packages in Sage have no spkg-check file, so self-tests are not run, even if the upstream source code has a test suite. I created a list of them at some point - see the first column only of http://trac.sagemath.org/sage_trac/ticket/9281 That list is probably not up to date. I've lost count of the number of spkg-check files I've created, but still more need to be done. > Also I think that SAGE_CHECK="no" should not trigger the check. Agreed. Five months ago John Palmieri wrote a fix for this, but as I remarked on the ticket (#9960) endless changes (which IMHO should have been on other tickets) were requested by the reviewer, so the patch is still not merged. Perhaps one day it will be. Dave -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
