[Distutils] Any thoughts on supporting e.g. Alpine Linux? (was: PEP 571: Any further manylinux2010 concerns or questions?

[Trishank Kuppusamy]

Hello Nick,

On Tue, Apr 3, 2018 at 7:59 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

>
> At the specification level, we'll need an update to PEP 425 that's
> comparable to Dustin's PEP 566 for the core metadata (which both
> defined metadata 2.1, and made
> https://packaging.python.org/specifications/core-metadata/ the stable
> reference URL for the latest version of the metadata spec).
>
> I'd like to see us do the same thing for platform compatibility tags:
> have https://packaging.python.org/specifications/platform-
> compatibility-tags/
> define the format, and use the PEP process to make changes to that
> living spec.
>
> While the primary motivating use case is distro-specific Linux wheels,
> we should at least consider the possibility of defining the new
> optional fields in compatibility tags in such a way that they could
> also be used for ABI compatibility levels in more centrally controlled
> platforms (i.e. Windows, macOS, iOS, Android), or to tag an expected
> deployment environment (e.g. letting the Galaxy Project folks mark all
> their internal wheels as "galaxyproject", and then configure their
> deployment environments to only accept wheels tagged that way).
>
> Such a spec update would cover points 1->3 above.
>
> At the implementation level, I don't have any great insight on how you
> might best go about pursuing that, but I suspect factoring out some
> useful helper functions into the low level `packaging` library may
> make sense (I believe Vinay Sajip's `distlib` already has some helpers
> along these lines that would potentially require updates). At a
> minimum, to be useful:
>
> * either setuptools+bdist_wheel need to be able to produce wheels with
> the more detailed tags, or else there has be a suitable wheel renaming
> utility available (akin to `auditwheel repair`)
> * twine needs to be able to upload wheels with the more detailed tags
> * warehouse needs to be able to accept uploads with the more detailed tags
>
> (For that last point, I'd personally prefer it to be a project level
> setting to opt-in to allowing uploads with the more detailed tags,
> such that the default behaviour is to reject them, and provide an
> opportunity for us to nudge folks towards manylinux wheels)


Sounds good. I'll take a stab at updating the PEP, and see. Can't make any
promises as to a timeline, but I'll get back when (and if) I have a draft!

Regards,
Trishank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20180403/1b29778f/attachment-0001.html>