[BugFix] FixSecForm13FHRFetcher: TypeError: Expected numeric dtype, got object instead.
#7171
Conversation
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
deeleeramone
added
bug
piiq
approved these changes
Jul 17, 2025
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 fixes a bug that the tests running in #7169 found. I would have expected tests to have previously revealed this, but it could likely be attributed to a higher pandas version.
To test this, upgrade the version of pandas to the latest, in your
obbenvironment, and then run the SEC provider's unit test.pytest test_sec_fetchers.py::test_sec_form_13FHR_fetcherBefore will raise a TypeError.
After, passes.