Merged
Conversation
tompollard
approved these changes
Mar 19, 2026
Member
|
Fixing this import might help. Here is the build log (with |
This file contains hidden or 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
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.
This PR removes an import of from the
dateutilpackage since it is not being used. The import had been added recently: 5ec257e.From what I gather, this was the only place that
dateutilwas being used. Sincedateutilwas not in ourrequirements.txt, this could be related to the current issue where our readthedocs site is not displaying the docstring details. Hopefully this fixes the Read the Docs rendering issue. The build logs show that only section outlines were rendered because autodoc failed to importwfdbafter hitting a now-removed, unuseddateutilimport that wasn’t installed in the docs build environment.