CI should be fixed - merge main to kickoff the builds.

Great thanks for the contribution @cdce8p

If you are interesting in further contributions, it might be a nice follow up to check all of the files we have and make sure that the Python include / macro always comes first. Probably worth turning off the clang-format feature that reorders includes to ensure that

Great thanks for the contribution @cdce8p

If you are interesting in further contributions, it might be a nice follow up to check all of the files we have and make sure that the Python include / macro always comes first. Probably worth turning off the clang-format feature that reorders includes to ensure that

I might be able to take a look at that. No promises though 😅

@WillAyd What is the process to get this fix backproted to 2.2.x / 2.3.x? Should I open a new PR targeting the corresponding branches? Tbh this is currently one of the blocking items adopting the new release and subsequently being reading for Python 3.13.

So the scope of this is that it prevents running pandas on 3.13 on musl platforms right?

The 2.2 branch I think is closed at this point. We are in the process of backporting a ton of things to 2.3, but I think also want to be very cognizant of what else goes there, because we have already spent a ton of time on that with very limited resources.

@lithomas1 @jorisvandenbossche @rhshadrach might also have opinions

So the scope of this is that it prevents running pandas on 3.13 on musl platforms right?

It prevent building pandas >=2.2.0 on musl with I believe all Python versions. I did the tests with 3.12 but the last working release 2.1.4 isn't compatible with 3.13 in the first place.

Given that this is a tiny diff, lets at least backport this to 2.3.x

@meeseeksdev backport to 2.3.x

It prevent building pandas >=2.2.0 on musl with I believe all Python versions.

If that is the case, would it be good to add a note about this in the 2.3.0 whatsnew file?