Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should fix the current CI failures. There were several issues, listed below from most trivial to least, all but the first were related to tests involving nightly builds of pandas (caused by changes that will be introduced in pandas 3).
reference-data
was needed for pyarrow 15.0.2.infer_datetime_format
argument fromto_datetime
. According to the docs this has been deprecated since version 2 and passing it has no effect._is_view
property will be removed from theDataFrame
class. Obviously using a private property is always a bit dubious, but it was only used for testing. My no-less-dubious solution was to pull the same information out of another private property :)numpy.array_split
is used to split aDataFrame
. As far as I can tell this only works becausearray_split
callsnumpy.swapaxes
here, which in turn uses callsswapaxes
on the underlying object through a getattr call. This will no longer work once the (currently deprecated)swapaxes
method is removed in Pandas 3. This is known to numpy maintainers (see this issue), and verdict appears to be that it was never intended usage and will not be supported going forward. Therefore, I added a workaround.