-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to build pydantic_core on OS X 10.11 with Python 3.10 #1295
Comments
The hint here is already in your build output:
If you update your Rust compiler (probably with |
@davidhewitt Unfortunately, starting from Rust 1.74, the minimum supported macOS platform is macOS 10.12 (see here), so the latest Rust compiler supporting OS X 10.11 is Rust 1.73. I tried installing the latest Rust using the standalone installer, but that did not work. If |
That's a great point. I think we should consider downgrading our minimum Rust to 1.73, but this may not be trivial. |
^ reflecting on the above, I think downgrading is the right thing, but I think the reality is that extending support backwards to old macOS versions is not a high priority for me right now. If anyone is interested in helping downgrade, a PR is very welcome. |
Could you please give some hints about how to contribute on this specific downgrading issue? |
The idea would be that you can check the compile against Rust 1.73 (for example) by running Or you could set the I expect that there are a couple of language features and stdlib APIs which we use which will need replacing. If it's not clear how to replace them, perhaps post back here with examples and I can give suggestions. |
Rust 1.73 is missing some features. MSRV can be lowered to 1.75, but not below. See #1315 |
I think 1.73 would still be reachable but it'd be a lot more work. |
Hi,
pydantic_core
>= 2.16 only provides wheels for macOS >= 10.12 and it would fail when compiling from source on OS X 10.11 with Python 3.10.11:pip3 install --upgrade pydantic==2.7.1
pip3 install --upgrade pydantic==2.6.4
The text was updated successfully, but these errors were encountered: