MNT: Remove beautifulsoup4 from docs requirements #2274
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I lean towards a new category for the dependency. |
beautifulsoup4 was not used in our docs build. It is brought in by pydata-sphinx-theme, but leave the dependency there. We do use beautifulsoup4 in SRTM tiles, but that has nothing to do with the docs.
Added in the optional |
dopplershift
approved these changes
Oct 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
beautifulsoup4 was not used in our docs build. It is brought in by pydata-sphinx-theme, but we can leave that dependency resolution there. We do use beautifulsoup4 in SRTM tiles, but that has nothing to do with the docs installation. Not sure if we want to move that into a different category or create a new one altogether
srtm = ["beautifulsoup4"]?