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
Segmentation fault on OS X 10.11 with Python 3.10 #7170
Comments
Thanks @BLKSerene for reporting this 🙏 @samuelcolvin , @davidhewitt do you have any idea? |
@BLKSerene are you able to share any more details about the crash, maybe a detailed crash log? |
@davidhewitt The only error message shown is (when simply importing
Is there any way in which I could get a more detailed crash log? |
Can you find them here? https://www.maketecheasier.com/read-macos-crash-reports-troubleshoot-mac/ |
@davidhewitt I found that this issue only happens with Here is the crash log (
|
Thanks. Reading that doesn't give me any substantial clues unfortunately. Given that it's fixed in 2.2.1 I suspect this was resolved by the removal of I think realistically we would struggle to test this, because we use the Github runners and if we tried to test all arch/os/python combinations it would be extremely broad. I'm going to close this as it sounds like the fix has already landed. (It's not expected that we will add |
Initial Checks
Description
Hi, it seems that
pydantic
v2 does not work on old macOSes such as El Capitan 10.11 with Python 3.10.I suspect that the problem is that
pydantic
v2 introducedpydantic_core
which is writen in Rust, and the Rust version used to buildpydantic_core
does not target at old macOSes.pydantic
officially support Python 3.7+ which then officially support macOS 10.9+. If there are requirements on the minimum version of macOS, a note in README would be helpful.A similar issue found in other projects: undertheseanlp/underthesea#677
Example Code
Error message:
Segmentation fault: 11
Python, Pydantic & OS Version
Selected Assignee: @hramezani
The text was updated successfully, but these errors were encountered: