ENH: Add Alpine to CI

[WillAyd]

Feature Type

• Adding new functionality to pandas

• Changing existing functionality in pandas

• Removing existing functionality in pandas

Problem Description

We have historically had some bug reports come from Alpine users but have never tested that platform in the past. Now that we have an open source Docker account we should be able to create an Alpine image for testing use

Related to #50046

Feature Description

see description

Alternative Solutions

I don't believe GH actions has an alpine image, but if it does that could work too

Additional Context

No response

[lithomas1]

I don't think we should commit to this until numpy tests Alpine in their CI.

IIRC, we do have a good chunk of users on Alpine. I think I ran the stats a couple of months back, and they were one of the most common platforms installing from sdist.

[WillAyd]

Yea my guess is Alpine will be the container of choice for any deployments of pandas within lambda functions

[kostyafarber]

Should we open an issue in nummy asking them to add Alpine to their CI?

[WillAyd]

Sure that would be awesome @kostyafarber

[kostyafarber]

@WillAyd numpy have closed the issue so I guess we can start making tracks on this now

[WillAyd]

Awesome!

[kostyafarber]

Happy to assist on this if needed. Pointing towards any resources/instructions would be helpful.

[WillAyd]

Awesome! Yea the pandas CI is housed in the .github folder - you might be particularly interested in the Workflows therein to extend or model this after.

We need a source image to start from. I don't know if GitHub actions has a musl image to build off of. If not I would see what numpy is using as their foundation, or could also use the alpine image from #50046

[sanmai-NL]

@WillAyd You can just use the Alpine Linux image, which is the main Linux distribution using musl libc right now.

[lithomas1]

Closing as this is completed.

[MrMino]

@lithomas1 @WillAyd do you have any plans for providing musllinux wheels (for PyPI)?

[WillAyd]

I think would be open to it but needs a community PR - would you be interested in trying that @MrMino ?

Note that we just recently approved PDEP-10 #52711 so we probably need pyarrow to distribute a musllinux wheel first.

[lithomas1]

I think Matt enabled musllinux wheels already for 2.1, but the point about pyarrow not having musllinux is a good point.

[MrMino]

Yup, seems like the relevant CI stuff is already there.

I also nudged the issue on the pyarrow side, it has been discussed before PEP-656 happened.