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.
Pandas 3 will remove the infer_datetime_format argument from to_datetime. According to the docs this has been deprecated since version 2 and passing it has no effect.
The _is_view property will be removed from the DataFrame 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 :)
In two places in the tests, numpy.array_split is used to split a DataFrame. As far as I can tell this only works because array_split calls numpy.swapaxeshere, which in turn uses calls swapaxes on the underlying object through a getattr call. This will no longer work once the (currently deprecated) swapaxesmethod 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.
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-datawas needed for pyarrow 15.0.2.infer_datetime_formatargument fromto_datetime. According to the docs this has been deprecated since version 2 and passing it has no effect._is_viewproperty will be removed from theDataFrameclass. 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_splitis used to split aDataFrame. As far as I can tell this only works becausearray_splitcallsnumpy.swapaxeshere, which in turn uses callsswapaxeson the underlying object through a getattr call. This will no longer work once the (currently deprecated)swapaxesmethod 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.