Re: Opinions on requiring younger glibc in manylinux1 wheel?
Paul Moore <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <CACac1F-t=Hkh6r8kkjVFTeO9yGouTVLN=+5bth_X7=Um8jH7xA@mail.gmail.com> |
On Tue, 18 Sep 2018 at 13:45, Olivier Grisel <[email protected]> wrote: > > > I would say there's value in having two official manylinux flavors at once, for example manylinux2010 for maximum compatibility (it's already 8 years old as far as requirements go!) and manylinux2016 for recent systems compatibility. Later, manylinux2022 gets released as the "recent systems compatibility" standard and manylinux2016 becomes the "maximum compatibility" flavor. > > That's an interesting proposition. > > Would pip be able to automatically select the most recent compatible wheel when two are available on PyPI? Pip determines a list of supported tag combinations and takes the first one that matches. So it's not "automatic", in the sense of needing nothing to be done, rather someone would have to contribute code to pip that determined whether (for example) the platform supported manylinux2016, and if so add it to the list of supported tags ahead of manylinux2010. That code would need updating as newer standards like manylinux2022 were finalised. Paul -- Distutils-SIG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/OSJLCWRGC4VVVEPUXAXZALIH36DA3ASG/