-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
DOC: pin sphinx to 1.8.5 #26781
DOC: pin sphinx to 1.8.5 #26781
Conversation
Context for doing this would be the styling changes introduced in sphinx 2, for which we should first update our custom css (described in #26058) |
cc @datapythonista @TomAugspurger If we would release right now, I would build the docs with sphinx 1.8.5 for the release. |
I think pin to 1.8.5 for now. |
Agreed pinning is fine (i think we have pinned sphinx in the past frequently) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on pinning
I'd probably migrate to sphinx 2 when we change the theme. And surely after we fail the CI on doc warnings.
But can you also pin the version in environment.yml
please, so we build the docs locally with the same version as travis.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and may be update the comment on pinning to why we're using 1.8.5, and duplicate it in environment.yml
too (I'll propose getting rid of this deps file again soon).
Updated |
Codecov Report
@@ Coverage Diff @@
## master #26781 +/- ##
==========================================
- Coverage 91.72% 91.72% -0.01%
==========================================
Files 178 178
Lines 50779 50779
==========================================
- Hits 46579 46575 -4
- Misses 4200 4204 +4
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #26781 +/- ##
==========================================
+ Coverage 91.72% 91.76% +0.03%
==========================================
Files 178 178
Lines 50779 50751 -28
==========================================
- Hits 46579 46570 -9
+ Misses 4200 4181 -19
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks
Ok travic job very good
Vào 12 Th6, 2019 13:47, Marc Garcia <notifications@github.com> đã viết:
@datapythonista commented on this pull request.
+1 on pinning
I'd probably migrate to sphinx 2 when we change the theme. And surely after we fail the CI on doc warnings.
But can you also pin the version in environment.yml please, so we build the docs locally with the same version as travis.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#26781?email_source=notifications&email_token=AJLD4SJOYLFKZHYXYERY3PLP2CLWZA5CNFSM4HW5UGBKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB3IOMOY#pullrequestreview-248571451>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AJLD4SJPJWRITYN4HBSMXULP2CLWZANCNFSM4HW5UGBA>.
|
ci/deps/travis-36-doc.yaml
Outdated
# recursion error with sphinx 2.1.0. https://github.com/pandas-dev/pandas/issues/26723 | ||
- sphinx==2.0.1 | ||
# some styling is broken with sphinx >= 2 (https://github.com/pandas-dev/pandas/issues/26058) | ||
- sphinx==1.8.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In conda files the version is specified with just one equal (==
is for pip, a bit confusing)
You'll also have to call ./scripts/generate_pip_deps_from_conda.py
to update requirements_dev.txt
, which is synched from environment.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you also need to remove one equal here, other than that looks good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering: does it actually matter? (it was with double equals before as well)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure, but we've got a function to convert them from one to two when synching, if we can have two may be better to leave two everywhere and simplify the synching
thanks @jorisvandenbossche |
xref #26058