-
Notifications
You must be signed in to change notification settings - Fork 522
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
automl broken with pandas 2 #1300
Comments
Thanks. Feel free to make a PR. |
Thanks @jgukelberger , @sonichi , I don't see the issue with pandas 2.0.3 and 2.2.2 numpy 1.24.3 |
That's interesting @sonichi. Attached is the full The only difference between the two environments is pandas:
Here's the full output of a failing test case:
And here when it works after downgrading pandas:
|
Thanks for reporting the issue, @Seyda1 . The error message shows that your data doesn't have a regular frequency. According to @jgukelberger 's feedback, pandas<2 doesn't have the issue. Could you try it and let me know if it works for you? Thanks. |
I got the same problem. The problem seems to be that FLAML expected |
I downgraded pandas to 1.5.3 as suggested, but I still encounter the same error. My parameter configuration includes:
|
Hi @Seyda1 , it's a limitation of FLAML that it currently only supports regular frequency. |
Hi @thinkall, thank you for the information. Is this an upcoming development, or should we wait longer? |
I'm afraid we'll need to wait longer. Contributions are very welcome! |
Several of the official examples and tests currently error out due to incompatibility with pandas 2.
For example, when following AutoML - Time series forecast in a fresh Python 3.10 environment,
pip install "flaml[automl,ts_forecast]"
currently installs pandas 2.2.2. Then, the first example raisesSimilarly, 3/9 tests in test/automl/test_forecast.py fail.
There's also #984, but that focuses on supporting pandas 2. In the meantime, the pandas dependency in setup.py should at least be constrained to <2 to avoid users ending up with a broken installation by default.
The text was updated successfully, but these errors were encountered: