On 08/30/2018 05:04 AM, Jeroen Demeyer wrote: > > I can see two solutions: > > 1. Get rid of "--optional=sage" completely. An added bonus is that this > would slightly simplify the doctest framework.
This is probably fine. Now that we have a grown-up build system, I see this as a consequence of a larger improvement. The way that most test suites work is that they test only the features that were enabled at build time. So, for example, ./configure --with-mathematica=/usr/local/bin/mathematica would build you a sage with mathematica support. The configure script would check that the binary exists and doesn't crash, and the "optional" mathematica tests would be run unconditionally under the resulting sage. We would still need separate long-time and internet test suites, but most of the "optional" test suites (including --optional=sage, since "sage support" is always enabled) could be eliminated in the same fashion. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
