Skip to content

Alternative wheel build #22668

Closed
Closed
@0181532686cf4a31163be0bf3e6bb6732bf

Description

Hi,

I'm about to start working on adding support for non-glibc linux platforms (Alpine etc)[1, 2] to the pip/wheel toolset (pypa/manylinux#37). Long story short, pip wheels don't support musl libc at this moment, so if you want to install pandas in a neat small Alpine-based Docker image, you have to compile it from scratch, whether ubuntu/centos/etc mainstream distros are handled by binary wheels perfectly. And if you want to build package by yourself, you have to install compiler toolchain and spend some time on compilation, thus neglecting all possible benefits of using small Alpine-based image.

So, the question is how the binary management should be handled the best way: I'm planning to setup Travis CI job which will build wheel for pandas along with other popular packages (numpy, scipy, opencv to name a few) against musl libc, but this wheel should be published somewhere. What do you think is the most efficient and secure way of getting this wheel uploaded onto pypi registry? Thanks!

[1] https://alpinelinux.org
[2] http://www.etalabs.net/compare_libcs.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    BuildLibrary building on various platforms

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions