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.
- [ ] offsets.Day DST behavior #44364
- [ ] #29962
- [x] #34916
- [ ]
Index.__eq__(Series)return NotImplemented #36759 - [x] concat with empty or all-NA entries #40893, #39122
- [x] #52676
- [x] Have MultiIndex attributes return tuple instead of FrozenList https://github.com/pandas-dev/pandas/issues/53531
- [x] https://github.com/pandas-dev/pandas/issues/54154
Comment From: fangchenli
We could redo the SQL API to add compat for sqlalchemy 1.4/2.0. #40686.
36893 is also related. We should come up with a solution to solve both issues.
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.
Comment From: jbrockmendel
@mroeschke can you confirm the axis=None box can be checked?
Comment From: mroeschke
Not completely, https://github.com/pandas-dev/pandas/pull/50593 did not add axis=None for sum, prod, var, std, sem
Comment From: mroeschke
@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?
Comment From: jbrockmendel
im fine re-purposing this
Comment From: jbrockmendel
think the axis=None one is still viable to get for 2.0?
Comment From: mroeschke
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