Repository navigation
Handle NaN TOMTOM matches in the descriptive report (pandas >= 3) - #139
Open
MCHRISTOPHE1 wants to merge 1 commit into
Open
MCHRISTOPHE1 wants to merge 1 commit into
MCHRISTOPHE1 wants to merge 1 commit into
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
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.
With pandas >= 3, missing TOMTOM hits (None in generate_tomtom_dataframe) become NaN, which passes the truthiness checks in create_tomtom_match_logos/create_descriptive_names, so
modisco reportcrashes with AttributeError: 'float' object has no attribute 'strip'. This converts NaN back to None when building tomtom_data. Added a regression test that fails on master and passes with the fix. Moved from jmschrei/tfmodisco-lite#80.