-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TYP: Remove _ensure_type #32633
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
TYP: Remove _ensure_type #32633
Conversation
@TomAugspurger do we also want to add a test and a whatsnew, or merge these changes into original PR? |
Thanks! This seems good for now. I don't think we would need any additional tests, but a whatsnew would be nice (fixed regression). |
ok can revert test. will add whatsnew. |
No harm in keeping the test. |
lgtm. w.r.t. test no strong preference, though do we see ourselves getting confused with that in the future? Maybe just my lack of familiarity with our subclassing, but not sure why we would want a reindex to return a different type than the caller |
I think we'll be able to track it back to this discussion. But yes, I think in general the return type on |
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon! If these instruction are inaccurate, feel free to suggest an improvement. |
* remove _ensure_type by TomAugspurger * mypy fixup * add test * add whatsnew
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff