Skip to content
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 Sphinx version and theme. #2676

Merged
merged 4 commits into from
Mar 2, 2017
Merged

Upgrade Sphinx version and theme. #2676

merged 4 commits into from
Mar 2, 2017

Conversation

ericholscher
Copy link
Member

I did some basic builds locally that looked and worked fine,
and we have a lot of users using 1.5 in requirements files.
We don't have a great way to stress test this,
but I think we should definitely push it out as a default.

I didn't touch the conda defaults because it doesn't update as quickly as pypi.

I did some basic builds locally that looked and worked fine,
and we have a lot of users using 1.5 in requirements files.
We don't have a great way to stress test this,
but I think we should definitely push it out as a default.
@ericholscher ericholscher added the PR: work in progress Pull request is not ready for full review label Mar 1, 2017
@@ -2,7 +2,7 @@
pip==8.1.1
virtualenv==15.0.1
docutils==0.11
Sphinx==1.3.5
Sphinx==1.5.3
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we still even need these as requirements for the code, since all the Sphinx interaction happens inside Docker. I guess for non-docker installs it's still required, so might as well update it.

@@ -102,7 +102,7 @@ def setup_base(self):

def install_core_requirements(self):
requirements = [
'sphinx==1.3.5',
'sphinx==1.5.2',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not 1.5.3?

Copy link
Member Author

@ericholscher ericholscher Mar 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ha, didn't see it was released -- also this was an old commit :)

@humitos
Copy link
Member

humitos commented Mar 1, 2017

For some reason Travis is not loading

There was an error while loading data.

and I can't see why it's failing.

@ericholscher
Copy link
Member Author

Yea, looks like their web UI is borked. I'm guessing it's probably fine (given one of the tests is passing). The bigger issue will be seeing how it works in production throwing it against a whole pile of user data :)

@humitos
Copy link
Member

humitos commented Mar 1, 2017

Yeah, and also those projects that works with 1.3.5 but not with a newer one (if that it's possible) and don't have Sphinx pinned... will be a mess. They will be force to create the reqs file or upgrade their docs.

@ericholscher
Copy link
Member Author

Yea, there are some backwards incompatible changes in Sphinx -- hopefully a lot of folks are pinning their requirements in this case, but it will likely break for some folks. Not a whole lot we can do about that though :/

@ericholscher
Copy link
Member Author

The Travis build seems borked for other reasons. Merging this.

@ericholscher ericholscher merged commit 8262381 into master Mar 2, 2017
@ericholscher ericholscher removed the PR: work in progress Pull request is not ready for full review label Mar 2, 2017
@stsewd stsewd deleted the upgrade-theme branch August 15, 2018 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants