-
Notifications
You must be signed in to change notification settings - Fork 1.1k
switch from pandas.util.testing to pandas.testing #901
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
Comments
I didn't find a time horizon when At this point I'm +1 for waiting and aiming this for our v0.8.0 milestone where we can bump pandas-min to this level. |
Looks like I think we're talking about going up to pandas 0.22 in pvlib 0.8, so let's make this a pvlib 0.8 milestone. |
I think this will only take effect in pandas 2.0, according to their versioning policy: https://pandas.pydata.org/docs/whatsnew/v1.0.0.html#new-deprecation-policy That doesn't mean we have to wait until then to make the switch. @wholmgren are you imagining a straightforward find and replace for this, or maybe something like importing the pandas functions in conftest and then doing |
If we're bumping the minimum pandas in 0.8 then can we just go ahead and do the switch now?
I was imagining a find/replace. I don't see any advantage to adding it to conftest but let me know if I'm missing something. |
Sure.
Only advantage I see is that if pandas changes it again, we would only update one file instead of many. Seems unlikely. Find/replace is fine with me. |
pandas.util.testing
is deprecated and we're supposed to switch to the functions in the public API atpandas.testing
instead.I'm not sure what the pandas version compatibility is for this. If there's a problem, we could use
try/except
statements to handle earlier versions of pandas. Or we could just do nothing until the min pandas we support is high enough.The text was updated successfully, but these errors were encountered: