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
We ran into the problem that read_fwf uses widths as an argument to define contigious intervals. But because of **kwargs, it will also accept width and not throw a warning or error. In this case it will produce the wrong output, but without seeing the typo, it;s hard to find out what went wrong.
Describe the solution you'd like
Instead of the argument widths, use a more distinguish / informative name like fixed_widths. Or if changing the name is not preferable, we can throw a warning when a width is used in read_fwf instead of widths
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem?
We ran into the problem that
read_fwf
useswidths
as an argument to define contigious intervals. But because of**kwargs
, it will also acceptwidth
and not throw a warning or error. In this case it will produce the wrong output, but without seeing the typo, it;s hard to find out what went wrong.Describe the solution you'd like
Instead of the argument
widths
, use a more distinguish / informative name likefixed_widths
. Or if changing the name is not preferable, we can throw a warning when awidth
is used inread_fwf
instead ofwidths
API breaking implications
Not sure
Example with using the correct argument
widths
Example using the wrong argument
width
:The text was updated successfully, but these errors were encountered: