-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
FutureWarning: Series.base is deprecated and will be removed in a future version #4300
Comments
I did a quick grep of the repo and cannot find the offending line Not sure where why this warning pops up. |
Same issue |
Getting the same warning. The code is here:
From what I can tell about the history of the .base method it's a relic of deeper connections to numpy. I think simply replacing |
Here's the code that produces this for me, it seems to be a combination of passing a pandas Series as the sample_weight.
Looks like it's happening for pandas>=0.23.0 because the pandas |
A simple way, ignore the warning. import warnings |
Ignoring warnings should never be a solution |
Suggestions are welcomed. :-) |
#4337 should eliminate FutureWarning |
* Remove all references to data.base Should eliminate the deprecation warning in issue #4300 * Fix lint
* Remove all references to data.base Should eliminate the deprecation warning in issue dmlc#4300 * Fix lint
* Remove all references to data.base Should eliminate the deprecation warning in issue dmlc#4300 * Fix lint
@XsongyangX 0.90 version was released on May 20, and the fix was made on July 4. So you'll see see the warning in 0.90. The next release (1.0.0) will not have the warning. |
Sorry, wrong click. |
I am using python3.7.2 with xgboost 0.81 and got a lot of the following error messages:
/Users/jianhuitian/Documents/Programs/Anaconda3/anaconda3/lib/python3.7/site-packages/xgboost/core.py:587: FutureWarning: Series.base is deprecated and will be removed in a future version
if getattr(data, ‘base’, None) is not None
How to get rid of this annoying issue?
The text was updated successfully, but these errors were encountered: