On Friday, April 8, 2016 at 6:50:19 PM UTC+2, William wrote:
>
> > But then there is nothing to do on the Sage side, this already works and
> is
> > totally standard.
Just because
> it is technically possible to do something and documented how to do so
> online, doesn't mean there is nothing to do on the sage side.
>
What I meant was: there is nothing that we need to implement to make it
work. As I also mentioned, it would surely be good to have examples and
documentation.
> > Much of the memory usage of the current docbuild is the huge intersphinx
> > data, and no amount of modularization would make that smaller.
> I disagree. If the elliptic curves docs aren't in Sage at all (say),
> then it certainly
> isn't going to make that stuff larger.
>
But not smaller either, unless you get rid of the intersphinx data. The
reference manual is already broken up into smaller chunks that are
processed independently. Breaking it up more is never going to give us a
significant improvement. We can only make sphinx more efficient or build
shittier docs. And there you are IMHO just throwing out the baby with the
bathwater. Remove (or making inaccessible) large chunks of our
documentation and/or disabling hyperlinks surely saves a lot of time and
ram when building the documentation. But why? If you don't care about the
documentation then just compile Sage without it in the first place ("make
build").
--
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.
