-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
API: Breaking Changes in 3.0 (without deprecations) #44823
Comments
We could redo the SQL API to add compat for sqlalchemy 1.4/2.0. #40686. To add to this. In #45660, seems like people have used the sqlite fullback class for other connection types for many years without any issue. If that is actually a popular use case, we probably should officially support it and expand our SQL tests. And this issue overlaps with #36893. |
@mroeschke can you confirm the axis=None box can be checked? |
Not completely, #50593 did not add axis=None for sum, prod, var, std, sem |
@jbrockmendel should we push this as breaking changes for 3.0 without deprecations or should we just start a new issue when we're toward the end of the 2.0 cycle? |
im fine re-purposing this |
think the axis=None one is still viable to get for 2.0? |
Could be possible. I think the ones not addressed take slightly different code paths so not sure if supporting that is straightforward. IMO it should be not blocking for 2.0 |
Discussed on today's call, this issue to discuss potential changes we may want to make in 3.0 that are too big or cumbersome to deprecate.
Index.__eq__(Series)
return NotImplemented DEPR: Index == Series should return NotImplemented #36759tuple
instead ofFrozenList
? #53531DataFrame.to_excel
to output unformatted excel file #54154The text was updated successfully, but these errors were encountered: