-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Split requirements/pip.txt #5100
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 requirements/pip.txt #5100
Conversation
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.
Good approach! I think we are close to have it ready for merging.
I'd like to be more aggressive on the split and have it properly separated.
Example: If I downloaded the git repo and want to build the Read the Docs documentation, I should only do pip install requirements/docs.txt
and then make html
should work and produce the desired docs _without installing anything no-needed` (django or whatever).
This will probably ends up on having repeated packages on the requirements, but that's fine to me because we want to be able to fine tune it: "use Sphinx 2.0 for our docs, but not for building user's docs"
|
||
# Docs | ||
sphinxcontrib-httpdomain==1.7.0 | ||
sphinx-prompt==1.0.0 |
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.
I suppose that these two packages are for building our own docs and not for building user's documentation. So, these should probably go into a different reqs file maybe.
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.
Wasn't aware of that these are only for RTD docs.
these should probably go into a different reqs file maybe.
Since these are RTD-only requirements, we can put it back in the pip.txt
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.
Well, they are not required to "run Read the Read software" but to build the docs of it.
So, basically, we should use this requirements/docs.txt
file in our own projects under readthedocs.io (https://readthedocs.org/projects/docs/)
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.
Okay.
I have separated them in docs.txt
and also add -r local-docs-build.txt
to install the other dependencies.
@@ -14,3 +14,4 @@ pylint-celery==0.3 | |||
prospector==1.1.6.2 | |||
# prospector 1.1.6.2 is not compatible with 2.0.0 | |||
pyflakes<2.0.0 | |||
Pygments==2.3.1 |
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.
I put this here because it was required to make the lint
tests.
This gets repeated here as it was already moved to the local_docs_build.txt
I tried to do exactly the same thing. But in the |
Do you know why we are doing that? Is it to document our django settings? On the other hand, in case that it's strictly needed, does the docs build just installing |
These lines.
I tried this.
I think that RTD docs needs the RTD-specific requirements ( |
We are using the extension
OK, we can open another issue to research about this later and try to have the minimal dependencies for our docs. |
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.
Please, revert the creation of docs.txt
, open a new issue to track that path and we will be ready to merge this PR from my point of view.
This is because we are importing |
@humitos
It would be great. Will open a new issue to track this. |
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.
Won't this cause our docs build to fail, unless we update our .readthedocs.yml
to point at a new config file: https://github.com/rtfd/readthedocs.org/blob/master/.readthedocs.yml#L6
@ericholscher |
This will go out with next deploy, so we have time to debug 👍 |
Fixes #3757