BUG: use concurrent.futures.ThreadPoolExecutor in distutils instead of multiprocessing.pool.ThreadPool

[GalaxySnail]

Use concurrent.futures.ThreadPoolExecutor in distutils instead of multiprocessing.pool.ThreadPool.

Fix #21026

[mattip]

Thanks @GalaxySnail.

[InessaPawson]

Hi-five on merging your first pull request to NumPy, @GalaxySnail! We hope you stick around! Your choices aren’t limited to programming – you can review pull requests, help us stay on top of new and old issues, develop educational material, work on our website, add or improve graphic design, create marketing materials, translate website content, write grant proposals, and help with other fundraising initiatives. For more info, check out: https://numpy.org/contribute
Also, consider joining our mailing list. This is a great way to connect with other cool people in our community and be part of important conversations that affect the development of NumPy: https://mail.python.org/mailman/listinfo/numpy-discussion

[GalaxySnail]

Should this be backported to 1.22.x and 1.21.x? According to scipy/oldest-supported-numpy, 1.21.4 is the oldest version that supports python 3.10. NEP 29 says 1.19+ will be maintained until 2022-06-21, but it seems that only security fixes are acceptable.

[mattip]

I don't think we ever declared support for android in NumPy, so it is not "critical" to backport but "nice to have". The final decision is up to @charris.

[charris]

I don't have a problem with backporting build fixups, but that would only be for NumPy 1.22, we generally only update the latest release.

[GalaxySnail]

Thanks!