Bug#1043240: transition: pandas 1.5 -> 2.1

[Rebecca N. Palmer]

On 10/12/2023 20:16, Julian Gilbey wrote:
 > [...]I'd be in favour of doing the pandas
 > transition now, which will allow Cython 3.0 to move into unstable.

Cython 3 is already in unstable; pandas is currently using cython-legacy.

And yes, my list of packages broken by pandas 2.x is those identified by 
builds and autopkgtests.

On 11/12/2023 17:31, Matthias Klose wrote:
> On 11.12.23 08:12, Matthias Klose wrote:
>> up to the maintainers. But please wait at least until the current 
>> pandas and numpy migrated to testing, e.g. that the autopkg tests of 
>> pandas and numpy triggered by python3-defaults pass.
> 
> I just nmued pyrle and sorted-nearest, having dependencies on 
> cython3-legacy, letting the pyranges autopkg tests fail. Once this 
> succeeds, pandas should be able to migrate.

pandas' testing migration is also blocked by its build-dependency on 
python-xarray, and xarray's on python-sparse and cfgrib.

If necessary, pandas can be built without xarray, but this skips some 
tests and probably adds some error messages to the documentation (the 
examples are run at build time).