Description
While chasing down a pip wheel issue, I noticed that the conda-forge Python 3.8.10 (build 1) package reports the macOS version as 10.16 still. Using Miniforge:
conda create -n py38_test python=3.8
conda activate py38_test
python -c "import platform; print(platform.mac_ver())"
will report
('10.16', ('', '', ''), 'x86_64')
After some digging, it appears that this is caused by building Python 3.8.10 with macOS SDK < 11, in which case macOS will report this fake version number to the process. The recent Python 3.9 packages from conda-forge were built with the macOS 11 SDK and report the true 57AB OS version number.
However, it seems that there were commits to the Python 3.8 branch to update the SDK right around the same time as the Python 3.8.10 build: https://github.com/conda-forge/python-feedstock/commits/3.8
I'm not familiar enough with how conda-forge builds are sequenced and uploaded to Anaconda.org to understand exactly what happened here, but would bumping the build number to 2 trigger another build, hopefully with the macOS 11 SDK this time?