-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
Split sage_setup.docbuild out to a separate distribution sage_docbuild #30010
Comments
Dependencies: #29847 |
Changed dependencies from #29847 to none |
This comment has been minimized.
This comment has been minimized.
Dependencies: #29950 |
This comment has been minimized.
This comment has been minimized.
Last 10 new commits:
|
Author: Matthias Koeppe |
Commit: |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:13
In the new
Why do this at all, and if you're going to do it, why not use |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:15
Thanks. This was a leftover from when I was using |
comment:16
Can you please add Edit: No, sorry, it's already there. I just built Sage and it build |
comment:17
Hm... it's possible that it is always built because its dependency sagelib is always built... |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:47
The directory structure looks very strange: inside
where indentations indicate levels of subdirectories. For example, I see New commits:
|
comment:49
Thanks for catching this! This commit should fix it New commits:
|
comment:50
Perhaps for another ticket, but shouldn't |
comment:51
Yes, a target |
comment:52
Replying to @jhpalmieri:
What works really well for me is |
comment:53
I get this at the start of doctesting:
leading to
and then I get other doctest failures:
These all have a similar form:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:55
I don't know how to reproduce the |
comment:56
Replying to @mkoeppe:
I did that and got the same failures. This was with Sage's own Python and #18272. Then I switched to just this branch and used homebrew's Python and got the same errors. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:58
Thanks for testing - I've found the problem now. As a leftover from the previous version of the branch, |
comment:59
Now the
|
comment:61
Sorry, thanks for your patience with this. I was using |
comment:62
Can you explain the
I don't know what |
comment:63
These dependencies point to |
comment:64
Okay, thanks, that makes sense. This is working for me now, both building from scratch and upgrading from #31344. |
comment:65
Thank you! |
Changed branch from u/mkoeppe/split_sage_setup_docbuild_out_to_a_separate_package to |
sage_setup.docbuild
, created in #19127, has very different dependencies compared tosage_setup
:It depends on
sagelib
andsphinx
,whereas the rest of
sage_setup
is for buildingsagelib
.We remove the nesting within
sage_setup
, creating a new top-level packagesage_docbuild
.We split it out as a separate pip-installable distribution package
sage_docbuild
.Using the
spkg-src
script, a pip-installable tarball can be generated, which could be uploaded to PyPI -- for the use by external packages that want to build documentation.This is preparation for #29868 (pip-installable packages sagemath-doc-src, sagemath-doc-inventory, sagemath-doc-html, sagemath-doc-pdf)
Depends on #31344
Depends on #31353
CC: @kiwifb @jhpalmieri @isuruf @mwageringel @haraldschilly @mezzarobba
Component: refactoring
Keywords: sd111
Author: Matthias Koeppe
Branch/Commit:
aaab1d3
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/30010
The text was updated successfully, but these errors were encountered: