-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manylinux2010 behaviour understand #187
Comments
|
So current solution, if it is possible build manylinux1 and manylinux2010, and if some new things not supported by manylinux1 is needed then only manylinux2010 wheel is produced? |
Well, just one wheel is built. And if that happens to be And every |
Ok. Thanks. My question is connected with question "What I need to upload to pypi?". "If there is any advantage of upload both wheels to pypi?" Now I have bases to think about this. |
That's still not completely clear to me. Do read the further discussions we had on keeping 1 or 2 wheels, and the link to the pypa/manylinux discussion in there, where I asked the same question and got an answer: pypa/manylinux#179 (comment) |
Is that OK with you? Can we close this issue and get the issues counter one down again? :) |
I have few questions about introducing manylinux210 to cibuildwheel.
Why manylinux2010 build both manylinux1 and manylinux2010 wheels (Why to do this if something can be compiled to manylinux1 then is no ned for manylix2010 ??)
What is some extensions need c++14 or c++17. The manylinux2010 container has proper compilers, but it may use some features not available for old images. (??)
The text was updated successfully, but these errors were encountered: