fix: fixes #171; brings more type checks for returned data #172
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.
Overview
search
queries onoccurrences
. For backwards compatibiity,execute
still returns aDataFrame
object, but sets data inOccResponse
asdict({total: int, results: DataFrame/dict})
. This fixes failingto_pandas
method.NotImplementedError
on callingto_pandas
for non-supported data typesFutureWarning
while concatenating DataFrame duringsearch
. NA value columns while being merged with non-NA ones was throwing this warning. We do the merges while paginating large queries as API supports only 10k records at a time. So, we merge these chunks into one. Resolution was to skip merge during the first one (when the original results DataFrame is empty).rst
->md
.Thanks.