Skip to content

MAINT: Unpin sphinx. #181

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

Merged
merged 1 commit into from
Apr 30, 2023
Merged

MAINT: Unpin sphinx. #181

merged 1 commit into from
Apr 30, 2023

Conversation

rossbar
Copy link
Collaborator

@rossbar rossbar commented Apr 30, 2023

Removes explicit pin from sphinx. IIRC, the one in environment.yml might be necessary because the dependency management of at least one of the executablebooks packages is not reliable on conda-forge specifically. Nevertheless, the requirements pin should be unnecessary, and I think we should endeavor to use the latest version of sphinx that we can support!

If the conda job fails, I'll re-add the environment pin.

@rossbar
Copy link
Collaborator Author

rossbar commented Apr 30, 2023

It looks like the pin for conda-forge is no longer required either, so this closes #138 .

The CI failure (which has just started popping up for 3.11) is unrelated.

@bsipocz bsipocz added the infrastructure Issues relevant to infrasructure, rather than content label Apr 30, 2023
@bsipocz
Copy link
Member

bsipocz commented Apr 30, 2023

Thanks @rossbar!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Issues relevant to infrasructure, rather than content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants