> 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?

-- 
Olivier
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-le...@python.org
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at 
https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/KT4IWSHYRF2MWRHSXQE3OYDY6RV4TWCJ/

Reply via email to