-
Notifications
You must be signed in to change notification settings - Fork 447
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
Support >= Pandas 2.0.0 #811
Comments
@dosu-bot Can you help debug? Here are the error logs
|
🤖 Thank you for bringing this to our attention. The error message suggests that the test is failing due to an The To debug this issue, we need to understand the specific changes in Pandas 2.0.0 that could be causing this behavior. Unfortunately, I couldn't find specific details about these changes within the repository. However, I would recommend checking the release notes or changelog for Pandas 2.0.0 to see if there are any changes related to aggregation functions that could be causing this issue. Once we have more information about the specific changes in Pandas 2.0.0, we can update the In the meantime, pinning the version of Pandas to <2.0.0 is a good workaround to prevent the CI from failing. I understand that this is not a long-term solution, and I appreciate your patience as we work to resolve this issue. SourcesThis response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
@dosu-bot Here are changes from Pandas 2.0.0
|
🤖 Hello, Thank you for providing the detailed error logs and context. The The error you're encountering is due to the upgrade to Pandas 2.0.0. The 'temp_diff' column, which is of integer data type, is being aggregated using the 'Avg' function. However, the error logs indicate an In the Pandas 2.0.0 release, there were several changes that could potentially affect this operation. One of the significant changes was the introduction of the new Another change that could potentially affect this operation is the enhancements to the To resolve this issue, you could try the following:
I hope this helps! If you have any further questions or need more assistance, please don't hesitate to ask. Best regards, SourcesThis response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
From here #861 (comment), @devstein @ljubon I'm wondering if there's any progress for supporting pandas 2.0 or if an ETA is available for this? |
pandas 2.0 is out for more than one year now. |
It looks like this was resolved on GitHub about 3 weeks ago. Would it be possible to get a new release out? |
Done in 0.22.0! Thank you everyone for helping get this over the finish line. Please let me know if you run into issues. |
Is your feature request related to a problem? Please describe.
CI is failing due to Pandas 2.0.0
Describe the solution you'd like
Support Pandas 2.0.0
Describe alternatives you've considered
Current solution is to pin <2.0.0
Additional context
https://github.com/jupyter-incubator/sparkmagic/actions/runs/4603955122
#812
The text was updated successfully, but these errors were encountered: