PYTHON-4079 Generate ManyLinux2014 and ManyLinux1 Wheels

[blink1073]

No description provided.

[blink1073]

The docs failure is unrelated, due to a DNS outage.

[ShaneHarvey]

In EVG we also build the manylinux1 wheels, can we add those as well? If manylinux1 wheels are no longer needed then could you update the changelog to mention we stopped releasing them?

[blink1073]

If manylinux1 wheels are no longer needed then could you update the changelog to mention we stopped releasing them?

I'd prefer that route since we don't support Python 3.6 anymore, should I also remove them from the EVG script?

[ShaneHarvey]

Sounds good to me. This comment from Oct 2021 shows 3.7 has 8% manylinux1 usage and 2% manylinux2010 usage so it seems fine to drop them now: pypa/manylinux#994 (comment)

[ShaneHarvey]

The next version is 4.7 which already has an entry below.

[blink1073]

Lol, fixed.

[ShaneHarvey]

Should we rename the PR to "Remove manylinux1 wheels"?

[caseyclements]

Is the removal of i686 unrelated?

[caseyclements]

If I understand correctly, manylinux1 wheels are Centos5. Is that what we were using before, and this upgrades to Centos7? We can't move to manylinux_x_y because it requires the new pip solver. Please respond if I've gotten any of this wrong.

I think I understand what's going on and why. Looks good!

[blink1073]

Both x86 and i686 were manylinux1, but we're going to try and bring both back. Yes, this is related so supporting older versions of pip that come preinstalled on stock Centos 7. See the compat table here: https://github.com/pypa/manylinux. If we bump to manylinux2014, then we'd still support CentOS 7 rh-python38, but not stock CentOS 7.

[ShaneHarvey]

I guess I also have one question: why not just keep manylinux1 until it becomes a maintenance burden? It seems like it doesn't cost us anything to keep building and publishing them. And it would benefit users on older distros.

[blink1073]

why not just keep manylinux1 until it becomes a maintenance burden

Looks like that can work:

• pymongo-4.7.0.dev0-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.whl
• pymongo-4.7.0.dev0-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.whl

[caseyclements]

@blink1073 All looks good. Two questions.

1. Do wheels names like this mean that they're cross-compiled: pymongo-4.7.0.dev0-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.whl

2. test-skip = "*-macosx_universal2:arm64" Does this mean that we build the wheel for apple silicon, but don't test it?

[blink1073]

Do wheels names like this mean that they're cross-compiled: pymongo-4.7.0.dev0-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.whl

It means the symbols used support both of those manylinux targets.

Does this mean that we build the wheel for apple silicon, but don't test it?

Yes, apple silicon is not yet available on GitHub Actions