James Butler

@esc Thoughts on what you would like to do to handle the failing (Linux py38_np118_32bit) test which is due to no 32-bit version available for Python 3.8 from anaconda?

Following the successful merging of this PR, tasks such as those mentioned in https://github.com/numba/numba/issues/7917 can be followups.

Will also need to address the following in this PR which drops Python 3.7: https://github.com/numba/numba/blob/64c06beb0551117efc3b3687d9d66734e391f603/numba/core/utils.py#L379-L387

@esc I've rebased to fix merge conflicts. https://github.com/numba/numba/pull/7920 should probably be finalized and merged first as it removes the currently outdated code. I'm not the author of that PR so...

Now that there are more merge conflicts since I originally fixed them up, how am I allowed to proceed here? I know there is a merge conflict due to a...

@esc and @gmarkall I’ve rebased again to fix up merge conflicts and the CI is green.

Similar to changes made in https://github.com/numba/numba/pull/7920, but that PR has seemingly become stale? I did not see this existing PR because it had fallen down to the 3rd page of...

@jcfr I can issue a follow-up like https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/pull/307 that would update the CI to use these latest versions and to update the default to 3.9.12 or I can do it...

This also allows to continue using the latest version of `numpy` which now only provides macOS wheels for macOS 10.14 and later. See https://github.com/numpy/numpy/releases/tag/v1.22.3. In general it is becoming hardware...

The minimum macOS version was last updated approximately 2 years ago (https://github.com/Slicer/Slicer/commit/dede0266e8495a8337874d8bf39852a7b71e5ff4) when it was updated with support of versions 10.13-10.15.