-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
conda support: strict requirements on core dependencies like sphinx 1.3.5 prevent using more recent version #2566
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
Comments
Example here: https://readthedocs.org/projects/xtensor/builds/4837277/ |
@ericholscher what about pinning I think this will fix a couple of issues with the old versions. |
Seems reasonable. Will conda properly install from conda-forge in our current setup? |
On the other hand, I'm thinking if we really want to have pinned packages in the core conda environment. I mean, I understand that it's needed by the common virtualenv build since RTD offers a way to "just write the docs even if you don't know sphinx or python" (by suggesting you to create the |
I don't think so, since there is nothing related to the |
Why pinning at all? Just requiring Users will have the freedom to require a more specific version in their |
Closgin in favor of #2714 |
The list of core requirements specified at https://github.com/rtfd/readthedocs.org/blob/499a74076f0debae09acc1d4c4eeeab03f8f557e/readthedocs/doc_builder/python_environments.py#L192 prevents requiring another version of sphinx in one's
environment.yml
.For example, if I depend on breathe, which requires sphinx>=1.4.0, this creates a conflict.
The text was updated successfully, but these errors were encountered: