-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Failures to compile yt against Python 3.12.6 binary (macOS-aarch64) #337
Comments
Related to astral-sh/uv#7525 This is sort of documented in the quirks here. Basically, there are references to the tools used to build the distribution and libraries assume that they should use the same toolchain that the Python distribution was built with and retrieve that information only to find the tools don't exist anymore (because this is a standalone build and all of the build tools are isolated from the final distribution). There may be some helpful discussion in the linked issue. Generally, we're not sure how to solve this yet. |
Thanks for the well written issue, appreciate it. |
Thanks for the quick reply and pointers !
Can you clarify what you mean by "libraries" here ? if you suspect |
I'm honestly still learning about this problem myself, so I can't give super clear guidance. I think it's a probably a combination of the build system and your configuration of the build system? You can see that variables in
Which will have things like:
We should probably strip these here? But I'm not sure what else what will break. Alternatively, uv can try to upgrade the variables when installed on a system. I think the solution further downstream (like in the build system or your library) is to detect the proper Xcode version on the system and use instead of relying on the one stored in the Python distribution? |
I couldn't find anything in yt's I feel like this should be patched in |
I am hitting the same problem. Not with Any suggestion for a good workaround here? Since this prevents me from using managed python installation, maybe support something like registering external toolchains, like rye does. This way I could manage (locally compiled) versions I need via As a workaround, I am using |
Sorry, last comment should have gone to https://github.com/astral-sh/uv as a workaround for this problem. I will open a ticket there. |
Hi, I'm new to using the pre-built binaries from this project, that I get from uv, and I'm not sure wether this is an issue with said binaries, uv itself, or the package that I'm trying to build, but I currently lean toward the first, apologies if this issue is misplaced.
So, what I'm observing is that I cannot build
yt
against the Python 3.12.6 binary (specificallycpython-3.12.6-macos-aarch64-none
). I haven't tried other Python versions but I know that building this package works against a locally compiled 3.12.6 binary (obtained with pyenv)Steps to reproduce (tarball from PyPI):
excerpt
(indeed,
/Applications/Xcode_15.2.app
doesn't exist on my system, but I do have Xcode 16.0 installed under/Applications/Xcode.app
)output head and tail
Steps to reproduce (from github)
The error message looks different so I'm also including this case in case it's relevant.
excerpt
Output head and tail
This feels like the kind of problem that could be documented on the Quirks page but I couldn't find anything relevant there, or in the issue tracker. Is this solvable or is it an inherent limitation in portability from using pre-build binaries ?
The text was updated successfully, but these errors were encountered: