Sage doc build currently aborts by default whenever sphinx emits a warning, and keeps a hardcoded whitelist of "admissible" warnings that needs to be kept up to date. This is very inconvenient for distros building Sage with system Sphinx, as every new version introduces new warnings: a fix was just committed for Sphinx 4.3 and now it is broken again with 4.4 due to new warnings.
This is equivalent to adding "-Werror" in C/C++ build flags of released software, which is widely regarded as bad practice, as there is a high change of breakage when updating the compiler. Can we please reconsider this policy? Fixing the warnings can still be a requirement for accepting tickets upgrading Sage's bundled Sphinx, but this would make things less painful for distributions. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/a1e1d357-f7a9-4993-b5c9-dd2b165606c9n%40googlegroups.com.
