Ronald Oussoren <ronaldousso...@mac.com> added the comment:
> Now, the next minor releases will be 11.0.1 (that has shipped already), > 11.1.0 (will ship soon), then either 11.1.1 or 11.2.0 (we don't know). The > next major version will of course be 12.0.0. > > The question is: for 11.1.x or 11.2.x, which are minor updates, should > the pypi/wheel tags increase to 11_1 and 11_2, or stay at 11_0? Has > that been decided, and will be applied consistently? (11_0 makes more > sense, and it is what wheel is currently applying) It depends :-) We should advise everyone to build for deployment target 11.0 (and or 12.0 next year *if necessary*), but IMHO we shouldn't enforce this is in the stdlib. If someone decides they want to build with MACOSX_DEPLOYMENT_TARGET=11.3 that's their choice and should be reflected in the result of get_platform(). We shouldn't default to that though just because you're building on macOS 11.3. Something we can work on is an informational PEP that describes the best way to build wheels on macOS, in cooperation with the PyPA, delocate, ciwheelbuild, and whoever else is interested in this. And then try to teach the tooling to do the right thing. In most cases it should be fairly easy to create wheels that target an earlier version of macOS (like the installers on Python.org). The annoying part are (C) libraries with configure scripts that can detect and use functions that aren't available on the deployment target. For most libraries that I've created bindings for (most of them in-house) this hasn't been a problem in practice, but that's a very limited sample. Sorry about going of on a tangent, none of this is relevant for this particular issue ;-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42554> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
