-
Notifications
You must be signed in to change notification settings - Fork 202
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
Unclear sphinx pin in pyproject.toml #583
Comments
Currently, installing sphinx-book-theme indeed downgrades the version of sphinx to 4.5 if the latest is installed (5.0.2), causing some downstream issues... |
@pradyunsg maybe I'm misunderstanding the checkmarks in the linked issue, but it looks like there's a discrepancy between the issue listing and the pin in Note also that my original comment was about the comment in the pyproject.toml - sphinx 4 is no longer the "latest" sphinx, so if the intention is to pin sphinx-book-theme to the sphinx 4 series for now (this seems to be the case) then the comment wording should be updated. It's a very straightforward change but I just want to make sure that I'm understanding everything correctly. |
Indeed, that checklist is for which repositories need to be migrated still. Those that are ticked are migrated and Sphinx-5 ready. The rest are not. I've updated the issuue title and text to more clearly reflect that. :) IIUC, the blocker for this theme is indeed docutils -- since Sphinx 5 allows using docutils 18 (and 19?) which has backwards incompatible changes. |
The comment here was out-of-date (sphinx 5 has been released) which made it unclear whether the pin was intentional or an error. From the discussion in executablebooksgh-583, it's now clear the pin is intentional, so removing the comment for clarity. Alternatively, the comment could be updated in a way that won't be obsoleted by future sphinx releases - wording suggestions welcome.
Describe the bug
The pyproject.toml contains the following pin:
sphinx-book-theme/pyproject.toml
Line 61 in 9ed62f5
From the comment, it is unclear whether this pin to the sphinx 4.X series is intentional or not, since "latest" == 5.X.
If the pin to sphinx 4.X is intentional, an update to the comment would be sufficient. FWIW the pin does seem to be important in that we have projects that build with sphinx 4.X but not 5.X, though I suspect the real problem is transitive dependencies (e.g. docutils). See numpy/numpy-tutorials#136.
Reproduce the bug
N/A
List your environment
N/A
The text was updated successfully, but these errors were encountered: