Thanks for your answer Antoine! Considering your first comment, there is a section in https://www.python.org/dev/peps/pep-0571 under "Backwards compatibility with manylinux1 wheels" that states "manylinux1 wheels are considered manylinux2010 wheels" and the same remark in https://www.python.org/dev/peps/pep-0599/ for manylinux2014 about compatibility with both manylinux2010 and manylinux1.
I agree we should bring this up in https://discuss.python.org/c/packaging/14. Especially because hopefully one day we can get rid of _GLIBCXX_USE_CXX11_ABI=0 and it is possible that will need a bit more coordination across the Python community. I'm happy to get a discussion started over there. On Fri, Sep 10, 2021 at 12:40 AM Antoine Pitrou <anto...@python.org> wrote: > > Le 10/09/2021 à 09:12, Philipp Moritz a écrit : > > Dear all, > > > > how do you think _GLIBCXX_USE_CXX11_ABI should be set for manylinux2014 > > (and manylinux2010) wheels? Should it be 0 or 1? Unfortunately I don't > see > > https://www.python.org/dev/peps/pep-0599/ or > > https://github.com/pypa/manylinux specifying it. I think for manylinux1 > the > > common wisdom was to set it to 0. It would then also make sense to have > the > > same setting for the later wheels since the manylinux* wheels are > supposed > > to be compatible with each other. > > Are they? Where it is specified that they should be compatible? > > > It would be great to have some clarity around this in the community and > > make sure we all use the same setting to avoid subtle incompatibilities. > > Perhaps this should be asked more widely on > https://discuss.python.org/c/packaging/14 ? > > Regards > > Antoine. >
