-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
Upgrade to Sphinx 1.8.5 #26451
Comments
comment:1
Note that there is nothing I can doctest here. |
Branch: u/saraedum/26451 |
Work Issues: is the patchbot happy? |
Commit: |
New commits:
|
Changed keywords from none to sphinx, conda |
comment:6
I'd rather upgrade Sphinx while we're at it. That's a good thing to do and I would need to do that anyway to test this ticket. |
comment:7
I was fearing that you would propose that ;) I am not planning on working on upgrading Sphinx in Sage (as I've got too many other things to worry about.) I don't know what has chahnged in 1.8.1 and whether we would want to upgrade at all. More generally, I don't know what we're aiming for here. I feel we don't have enough people to keep Sage-the-distribution close to upstream most of the time so that's probably not what we should be aiming for? That said, feel free to upgrade Sphinx :) But if anybody likes these small changes and we want to move the Sphinx upgrade into a separate ticket, I would prefer that. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:9
Upgrading sphinx requires further changes to make docs build. I have a minimal patch at https://git.archlinux.org/svntogit/community.git/tree/trunk/sagemath-doc-sphinx-1.8.patch?h=packages/sagemath-doc |
This comment has been minimized.
This comment has been minimized.
comment:11
Antonio, does Sphinx 1.8.1 work with just those changes (even if there are deprecation warnings)? If so, we might as well upgrade. |
comment:12
Replying to @jdemeyer:
Yes, with Julian's patch and mine introspection works and docs build correctly. |
This comment has been minimized.
This comment has been minimized.
Changed work issues from is the patchbot happy? to none |
Changed author from Julian Rüth to Julian Rüth, Jeroen Demeyer |
comment:14
jdemeyer, did you forget to push your branch? (you added yourself as an Author but did not push any changes it seems.) |
comment:15
Please give me time... |
comment:16
Note that there is a licensing issue in sphinxify.py, see #26453. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:127
Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually) |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:130
PDF documentation builds fine for me. |
comment:131
looks good to me. |
comment:132
Great! Now we need to silence all of the stupid deprecation warnings. |
comment:133
See #27578 for a ticket to stop using the deprecated |
comment:134
Merge conflict |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:136
Rebased. |
Changed branch from u/jhpalmieri/26451 to |
This ticket upgrades Sphinx to version 1.8.5.
Our previous upgrade was to Sphinx 1.7.6 in #26033.
Tarball: https://files.pythonhosted.org/packages/2a/86/8e1e8400bb6eca5ed960917952600fce90599e1cb0d20ddedd81ba163370/Sphinx-1.8.5.tar.gz
Depends on #27528
CC: @timokau @kiwifb @antonio-rojas @embray @slel @jhpalmieri @dimpase @tobihan
Component: packages: standard
Keywords: sphinx, conda, upgrade
Author: Julian Rüth, Jeroen Demeyer, John Palmieri, Tobias Hansen
Branch/Commit:
f1a08e3
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/26451
The text was updated successfully, but these errors were encountered: