Re: Opinions on requiring younger glibc in manylinux1 wheel?
"Antoine Pitrou" <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <[email protected]> |
Nathaniel Smith wrote: > It's naughty, you shouldn't do it, and the energy you put into making > pseudo-manylinux1 wheels could probably be better put into making finishing > up the manylinux2010 work – there's not that much to do. Can you explain what's missing? Paul Moore wrote: > 1. It sounds like manylinux2010 may be what you want. Definitely. > 2. Maybe there's value in a tag that emphasises "current hardware" more than backward compatibility? 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. Regards Antoine. -- 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/ZZQP4KU7BLPFYRDLSFMWBDC4RUBJCZRH/