New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build documentation of cvxopt #24447
Comments
comment:1
From spkg-install:
The script mentionas 1.1.5. However, we now have 1.1.8.p2. And in the upstream tarball, I find
So, the docs are in fact not shipped by upstream. And building the documentation still requires Sphinx. But isn't the Sage documentation built using something related to Sphinx? I guess one should (on a different ticket) enhance Sage's machinery of building its docs, so that it can be used to build documentation of a third-party Python/Cython package. Admittedly I'm being selfish here: My group cohomology spkg would be the same case. |
Changed branch from u/SimonKing/build_documentation_of_cvxopt to none |
comment:3
I tried to build the documentation. But alas, it won't work. Apparently there is something missing in Sage's sphinx:
So, is it acceptable to add 'sphinxcontrib-websupport' into Sage's sphinx package? |
comment:4
Replying to @simon-king-jena:
Is Therefore, I propose that the spkg-install script for sphinx is extended by
Then, as I just tested, the documentation for |
comment:5
WTF? I tried to add
However, if I do Why is that? How can one use |
comment:6
Perhaps
? At least it seems to work! |
Author: Simon King |
Commit: |
comment:9
For info, More concretely, I think |
comment:10
Duplicate of #14645. |
When building Sage with
SAGE_SPKG_INSTALL_DOCS=yes
, cvxopt fails as follows:I guess one either has let the install script create a missing directory, or needs to configure with
--docdir=...
.Component: packages: standard
Keywords: cvxopt documentation
Author: Simon King
Branch/Commit: u/SimonKing/build_documentation_of_cvxopt @
ac5b90b
Issue created by migration from https://trac.sagemath.org/ticket/24447
The text was updated successfully, but these errors were encountered: