-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comparison of two pandas "period"-Columns is always False/not working #336
Comments
Just out of the office today but will take a look into this tomorrow. |
sorry for the delay. Finally been able to look into this. Can you tell me what version you are using? Using the latest dev branch there is a fix i think in there which solves this issue: #335 Running this with the MVE I get:
|
This should be fixed in the latest v0.14.0 release. |
Hi @fdosani , thanks for your reply, I can confirm its fixed in 0.14.3. Thank you! |
Hi,
we have multiple cases where we have to work dates that don´t fit into the pandas "datetime64[ns]" type. We are using pandas Period as a replacement.
when comparing dataframes with period-Columns, datacompy always returns all rows as non-matching, even if they should match. Below an example:
I´ve left an larger dataframe with additonals columns in the example code. The behaviour does not change if additonal columns are present.
I tried to adjust "abs_tol" with no luck.
If you can point me to the right direction in your codebase, I´m willing to try to provide a PR.
Best regards
The text was updated successfully, but these errors were encountered: