You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is already a relevant issue, whether open or closed, comment on the existing thread instead of posting a new issue.
I couldn't find any nanoplot issue related to this
Description
Hi! I wanted to make a nanoplot using a column in a dataframe. I found that columns with uint datatypes incorrectly fail a check for being scalar datatypes, which breaks nanoplot functionality for them.
This leads to an error TypeError: 'NoneType' object is not iterable
Expected result
The example with a UInt32 column should've been able to create nanoplot just like the working example. The values aren't any different, just the datatype.
_str_detect uses re.match, which fails to match "int" with "uint" because it checks for a match at the beginning. Replacing with re.search fixes the problem because it looks for the pattern anywhere in the target, instead of just the beginning. I don't know if this has repercussions elsewhere though.
P.S. Thanks for the cool library! 😄
The text was updated successfully, but these errors were encountered:
Prework
Description
Hi! I wanted to make a nanoplot using a column in a dataframe. I found that columns with
uint
datatypes incorrectly fail a check for being scalar datatypes, which breaks nanoplot functionality for them.Reproducible example
Works
Does Not Work
This leads to an error
TypeError: 'NoneType' object is not iterable
Expected result
The example with a
UInt32
column should've been able to create nanoplot just like the working example. The values aren't any different, just the datatype.Development environment
Additional context
I think I isolated the cause to this line.
_str_detect
usesre.match
, which fails to match"int"
with"uint"
because it checks for a match at the beginning. Replacing withre.search
fixes the problem because it looks for the pattern anywhere in the target, instead of just the beginning. I don't know if this has repercussions elsewhere though.P.S. Thanks for the cool library! 😄
The text was updated successfully, but these errors were encountered: